I read with great interest the articles on embedded Linux and, in particular, the applications for handheld devices in the September 2000 issue of Linux Journal. I would like to emphasize though, that while the author of the article (“Compaq's Approach to Linux in Your Hand”) correctly points out the lineage of the iPaq as being the Itsy project at Compaq, one should be aware that Intel's Assabet reference design also contributed to iPaq's development. This is clearly seen when one looks at the system specification of the iPaq; this verifies that the system control registers are similar to the Assabet design. In particular, the unique audio codec solution on the Assabet has been identically implemented on the iPaq design. The Assabet platform is based on Intel's StrongARM* architecture (recently renamed as Xscale*), compatible SA-1110 processor and SA-1111 companion chip. The Assabet design offers significant technical attributes over the Itsy design, specifically the stereo audio, color display, power management, CF support and backlight to name a few.
Key developers of the Assabet platform are at a new company called ideaLogix, which is currently developing wireless video streaming products and services for visual information management.
—Jumbi Edulbehram email@example.com
Thank you for the good article “Good-bye Bandits, Hello Security” in October 2000's From the Editor column.
I believe it is of vital importance to do a follow-up study of the major Linux distributions such as Red Hat, SuSE, Debian, Slackware and about 20 more, and see to what extent security is implemented in the next versions. Please examine the security, ease of use and default setup from installation program. With such a study, LJ will force the major distributions to set standards for this issue. As you mentioned in your article (aimed at distributors?, good) there are many new Linux users hooked up permanently by DSL or cable, and if security is not set up by default, or is too difficult, they will choose some other OS (I will not spell it out).
—Bertil Palmqvist Bertil.A.Palqvist@telia.se
I was reading “Securing DNS and Bind” in the October issue and noticed an error that some beginners to DNS may not understand. When talking about the computer querying for an IP address to wiredmonkeys.org (or whatever it was), the author states that it will look to ns.isp.org instead of ns.someisp.org. This can be confusing to people who may wonder why it would leave their domain (someisp.org) and search a name server in isp.org.
—Brandon Shirey firstname.lastname@example.org
I'm shocked at your response to Dale Lakes' letter in the September issue (Disgusted, page 6). It is ridiculous for a magazine like yours to hire a company which uses NT and IIS to fufill your web hosting and e-commerce needs.
Don't you get it?
The Linux OS needs the support of the IT community. We need to be able to answer the objections of corporate managers and home users who can't think outside of the Microsoft Box. We all need to prove to our friends, family, coworkers—everyone!—that we can expect a PC to be reliable, stable and secure. We don't have to be overcharged for less than promised. We can concentrate on using our computers rather than being used.
However, when a Linux magazine has to rely on Microsoft to have a web presence, you make us all look like fools. You'll have no credibility and deserve none until you start practicing what all of us are preaching every day: “Expect More—Use Linux!”
By the way, your response said you're looking for a company that can do web hosting and e-commerce on Linux. My Google search (http://www.google.com/) returned 97,000 hits. Three of the companies listed had ads in your September issue.
—Randy Cook email@example.com
I would like to respond to the reader whose letter was published in the September 2000 issue of Linux Journal under the headline “Disgusted”. The author complained because Linux Journal's e-commerce and fulfillment partner (that's us) runs the Linux Journal Store web site (http://store.linuxjournal.com/) on Microsoft NT and IIS.
While the complaint is accurate, it doesn't begin to discuss how we use computing resources at WAS Inc. Let me say to this customer, and every other potential customer, that our use of technology is completely subordinate to the task at hand: satisfying the shopper. We don't pick operating systems due to popularity, we pick them for their suitability to our needs. (For various reasons, NT happened to be the best choice for our internally-developed software. We use, in addition to NT, Linux, IBM AIX, OS/2, PC-DOS 7, Mac OS and Windows 98. All singing, all dancing, all SAMBA-ing.)
We are, in fact, currently in the process of moving from NT to AIX as our primary platform, for the same reason: NT did not meet our needs. We discovered some serious scalability problems and needed to think hard about our platform of choice. We write our own e-commerce software (we do not use Microsoft's), so we have more invested in object-oriented technology and our current code structure than we do in any one operating system. Our product runs today on OS/2, Windows NT, IBM AIX, Sun Solaris and HP-UX. We'd be on Linux today if IBM supported our language there. (Please write and ask them to make VisualAge Smalltalk available on Linux.) We will be on Linux in the future even if they don't. But our immediate move will be to AIX on RS/6000 systems.
While I appreciate your correspondent's feelings, I wish he knew us better. We're Linux fans and Linux friends. We've run Linux since our first distribution—that's Softlanding Systems (SLS) 0.99. (I don't even know if they're around any more.) We did not discover Linux when Red Hat came along. I've personally been a Linux Journal subscriber in the past, way back in the first year. (I admit that now I read the back issues as they come into the warehouse—don't tell anyone.)
NT made business sense once. Linux and UNIX make more sense to us for the future than Windows 2000. This is where we get off the MS Windows boat. I would think our correspondent would be cheering.
We're not Redmond's mind slaves!
—Les Kooyman Vice President, WAS Inc.
|Dynamic DNS—an Object Lesson in Problem Solving||May 21, 2013|
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
|Non-Linux FOSS: Seashore||May 10, 2013|
- Dynamic DNS—an Object Lesson in Problem Solving
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- New Products
- A Topic for Discussion - Open Source Feature-Richness?
- RSS Feeds
- Drupal Is a Framework: Why Everyone Needs to Understand This
- Validate an E-Mail Address with PHP, the Right Way
- Readers' Choice Awards
- The Secret Password Is...
- Reply to comment | Linux Journal
3 min 55 sec ago
- All the articles you talked
2 hours 27 min ago
- All the articles you talked
2 hours 30 min ago
- All the articles you talked
2 hours 31 min ago
6 hours 56 min ago
- Keeping track of IP address
8 hours 47 min ago
- Roll your own dynamic dns
14 hours 1 min ago
- Please correct the URL for Salt Stack's web site
17 hours 12 min ago
- Android is Linux -- why no better inter-operation
19 hours 27 min ago
- Connecting Android device to desktop Linux via USB
19 hours 56 min ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi
It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?