Product Review: Corel's NetWinder
Right away, I was presented with WebFront, Corel's administrative interface for the WS. It took me awhile to figure out how to log in to the administration utility. After chasing through some of the CGI scripts under the /admin directory, I found a reference to /usr/bin/htpasswd.sh which apparently you must run at least once in order to get WebFront to realize your admin user is legit. This script creates the .htpasswd file.
WebFront is a browser-based tool that makes it possible to administer your NetWinder through a few simple forms. You can add, delete or modify users and groups through the interface. The clean, simple interface also serves up statistics on your NetWinder's performance in a graphical form, giving you glimpses of your web site's activity over different time scales.
To get a feel for its performance, I uploaded a few web sites that were done in Microsoft FrontPage. The transfer was very fast, a testament to the NetWinder's zippy little combination of processor and network architecture. I did a couple of these, one for our SF magazine TransVersions and another for a customer's intranet. Both sailed by faster than the “time to go” in FrontPage could keep up. What it estimated would take three plus minutes flew past in less than ten seconds.
Access to the pages was very fast. I fired up Netscape and as fast as I could click links, pages appeared in my browser. It was almost disconcerting. My local Pentium-powered Linux system, which we use as our corporate gateway/e-mail server/development machine, seemed to crawl in comparison. I was starting to get a touch of server envy.
Corel benchmarks with 16 clients connected to the NetWinder at 70 requests per second or nearly 350,000 bytes per second. You can expect as many as 150 concurrent requests per second, depending on client load.
My experience wasn't all roses. One of the things my company does regularly is set up Internet gateway, e-mail server, firewall, dial-on-demand combination systems that give customers inexpensive access to the Internet. We use PPP and masquerading to quickly link up a small office for transparent access. I decided to try this with the NetWinder.
Using the supplied netconfig, I found no option for modifying the PPP interface, so I created one using the Red Hat netcfg utility and tried to activate it. A message to the console informed me, “Sorry—this system lacks PPP kernel support”. No problem, I thought. I'm a UNIX guy. I can recompile the kernel with PPP support and be on my way. It turns out I was mistaken. There is no kernel source on the system, so PPP is impossible at this time.
Another thing I found disconcerting was the lack of an “off” switch. Call me foolish, call me irresponsible, but I find the fact that you can't shut down the machine distressing. While I realize you'll want your network gateway to stay up forever, I'm used to powering down my system every once in a while. If you want to shut down the NetWinder, you can use the standard shutdown command and wait for the “System halted” prompt before disconnecting power by pulling the power cord. That's right. You disconnect power, rather than turning it off. Even then, the FAQ from the netwinder.org site says you should not power down. The NetWinder has no battery for backup of its system clock. What it does have is a “big capacitor” that will hold a charge for about two days—any longer and you may need to reset your clock. When I got my NetWinder for evaluation, it had been off for some time and seemed to think we were already in the next millennium.
One other thing I will admit is fairly minor. I find the fan a bit loud, which is silly since the NetWinder is still quieter than my usual server. Without the hum of the power supply, the disk churning away and all the other noises one usually expects from their computer, the NetWinder's little fan seems, well, loud—bizarre.
A little later, I wrote up a small list of “would-be-nices” to pass along to Corel. I'd like some kind of database. The freeware Postgres would be enough to make me happy. I'd also like that PPP support, a built-in fax modem and the source code so I could hack my kernel when I felt the need to.
The next day, I called Corel's tech support engineers and discussed this. They told me that in early 1999, NetWinder would have PPP support and should include a V.90 modem for access. This pleased me very much. Right now, the NetWinder is designed to sit behind a router with one interface configured for the internal network and the other (most likely the 10 Mbps interface) hooked up to the outside world. This makes it a winner with small ISPs and corporate intranets.
The Corel engineers have already considered many of these things. After chatting with them, I was told that future NetWinders would include full Red Hat distributions which should take care of most of my software concerns. They have some other cool ideas as well. Corel intends to offer customized NetWinders using swappable daughter cards; some would come with ultra-wide SCSI to plug into RAIDs, others with ISDN. Corel is keeping an open mind.
The LC was out at the end of 1998. The WS and DM are available now. Corel is also looking into a TC or thin client. It would run a core Linux OS and take everything else from the network. Because it will be essentially diskless (OS on board), this NetWinder will be completely silent; it wouldn't even need a fan.
Ah, yes, the fan—Corel also thinks the fan is loud and is currently working with different designs to make things quieter.
|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|
- RSS Feeds
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- Dynamic DNS—an Object Lesson in Problem Solving
- New Products
- Validate an E-Mail Address with PHP, the Right Way
- Drupal Is a Framework: Why Everyone Needs to Understand This
- A Topic for Discussion - Open Source Feature-Richness?
- Download the Free Red Hat White Paper "Using an Open Source Framework to Catch the Bad Guy"
- Tech Tip: Really Simple HTTP Server with Python
- Please correct the URL for Salt Stack's web site
2 hours 58 min ago
- Android is Linux -- why no better inter-operation
5 hours 13 min ago
- Connecting Android device to desktop Linux via USB
5 hours 42 min ago
- Find new cell phone and tablet pc
6 hours 40 min ago
8 hours 9 min ago
- Automatically updating Guest Additions
9 hours 17 min ago
- I like your topic on android
10 hours 4 min ago
- This is the easiest tutorial
16 hours 40 min ago
- Ahh, the Koolaid.
22 hours 18 min ago
- git-annex assistant
1 day 4 hours 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?