Linux and The Linksys EtherFast Instant GigaDrive
Manufacturer: The Linksys Group, Inc.
Price: $695 US
Reviewer: Bill Ball
The explosion of small-business and home-office networking has made on-line storage, print service and IP addressing critical issues for many installations. Enter Linksys with a Red Hat Linux-based solution, the EtherFast Instant GigaDrive. This product provides 20GB of instant storage to your Linux or “other operating” system LAN without the hassle of adding a keyboard, monitor or mouse.
Linksys has been a Linux-friendly hardware manufacturer for a long time. Most network-savvy Linux users know that Linksys was the first company to list Linux as a supported operating system on the outside of its networking products' boxes.
I recently spent the afternoon playing with this new network toy from the Irvine, California-based company. The GigaDrive is one of those new breed of small network storage boxes you plug in to a hub on your LAN, turn on, web administer, use—and fall in love with.
Hooking up this compact device to your network is a snap. In this review, I will cover some of the basics and features of this new, first-generation, Linux-based networking product.
The box weighs five pounds, measures 8'' wide, 11'' long and 3'' high and includes a parallel port and an RJ45 jack. A small switch is used on the back when you connect the GigaDrive to a LAN hub or directly to a PC. Indicator LEDs on the front show remaining hard-drive capacity, power, status, hard-drive activity, NIC activity and whether DHCP service is being used.
The GigaDrive is basically a single-board, 45.26 BogoMIPS Pentium computer with (contrary to earlier reports on the Internet) only 16MB RAM, and a spacious 20GB drive running Red Hat Linux 2.0.36. The file system is installed on a 154MB root file system, and a 33MB swap partition is configured as a separate partition. The rest of the 20GB drive is devoted to a Linux EXT2 native file system, leaving nearly the entire drive available for storage of your LAN's or users' data.
When in use, several megabytes of memory remain free, as the majority of memory is used by normal Linux processes, such as the LDP printer dæmon, Apache, the AppleTalk atalkd dæmon and Samba's smbd dæmon. The default swap partition should be barely (if at all) used under load.
A small, 30-page manual, Windows NT install disk and CD-ROM for Windows-based installation are included. The machine is initially configured by running, of all things, a Windows-based setup and configuration program. Why support for Linux-based configuration and installation is not included is beyond me. A convenient Win client provides initial setup, such as IP assignment and setting of the date and time.
Linksys has prepared this device as a hands-off Linux system. This means that (supposedly) your only interaction with the GigaDrive is meant to be through a Netscape web page. After connecting the unit to your LAN, pressing the power button and waiting a few minutes, you can set the GigaDrive's server name (I called mine “gigi”), system date and time, IP address, Windows workgroup name and AppleTalk zone.
You can also configure the GigaDrive as a DHCP server, in which case you'll need to specify a range of valid IP addresses. The GigaDrive can also be configured to obtain its IP addresses from another server.
After assigning an administrative password, I could manage the GigaDrive remotely, using a URL like this:
The Connect window lists the GigaDrive, presents information on your unit and offers an Administer button. Click this button to administer the GigaDrive, and you'll see a dialog with numerous buttons to configure the system and administer users or shares on the drive, as shown in Figure 2.
The configuration buttons provide changes to networking, the system, utilities and status information. These are handy for changing the IP address, setting network features (such as turning DHCP on or off), adjusting date and time settings and troubleshooting. The GigaDrive can even e-mail you if there's a problem!
The storage management buttons allow you to browse the visible or “public” portions of the GigaDrive's hard drive and administer groups, shares and users. If you're new to Windows networking, you'll want to read the GigaDrive manual for a quick tip on how groups, shares and users are viewed by Samba, which provides networking storage and printer sharing. Plug a printer into the GigaDrive's parallel port, and you have an instant networked printer and print server. Windows users will find the GigaDrive and any attached printer under Network Neighborhood.
|Non-Linux FOSS: libnotify, OS X Style||Jun 18, 2013|
|Containers—Not Virtual Machines—Are the Future Cloud||Jun 17, 2013|
|Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer||Jun 12, 2013|
|Weechat, Irssi's Little Brother||Jun 11, 2013|
|One Tail Just Isn't Enough||Jun 07, 2013|
|Introduction to MapReduce with Hadoop on Linux||Jun 05, 2013|
- Containers—Not Virtual Machines—Are the Future Cloud
- Non-Linux FOSS: libnotify, OS X Style
- Linux Systems Administrator
- Validate an E-Mail Address with PHP, the Right Way
- Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer
- Senior Perl Developer
- Technical Support Rep
- UX Designer
- RSS Feeds
- Introduction to MapReduce with Hadoop on Linux
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?