An Ideal Appliance?
To put it bluntly, the Teak 3018 isn't as advertised. The BIOS is its only firmware. No operating system, firewall, routing software or anything else that would qualify it as a “Network Security Appliance” comes with the box. The real story is that the 3018 is simply a general-purpose platform that can be made into pretty much anything your geeky heart desires. Be that as it may, it isn't anything out of the package but a bare-bones system. It's not a network security “appliance” as delivered. It's a system designed for OEMs to build into network security appliances.
As an OEM system, the Teak provides a good solid hardware platform, but it's not without a few serious flaws. There are two basic classes of beefs I have with the thing: hardware problems and documentation issues.
Although the selection of the hardware that goes into the Teak is deliberately Linux-friendly, the way the hardware is put together isn't particularly impressive. To begin with, in both of the systems we received, the wireless antenna wires were routed through the cooling fins on the CPU heat sink—not an auspicious way to string a thin-gauge coax, to say the least. Sharp bends over sharp edges not only abrade the insulation, they also mess with the impedance of the cable, which can cause RF signal loss and other nasty problems.
The internal layout problems don't stop there. The wireless chipset isn't on the motherboard, but is instead plugged in via a MiniPCI wireless card, which sits on a riser card floating above the motherboard. This would be a fine arrangement if the card didn't sit directly above the CompactFlash card slot and cover it so completely that it's not possible to load or unload a CF card without pulling out the wireless apparatus. If you're wanting to use a hard drive instead of a CF card, you're still going to run into some trouble. The system includes a handy drive-mounting cage that will hold your 2.5" IDE drive almost exactly the right distance from the controller port for the included hard drive cable to reach. “Almost” is the keyword here. The supplied flat cable had been crimped into a rough cylinder by a pair of tie-wraps, leaving no slack in the cable and putting excess stress on both connectors. This isn't a good idea, as it introduces unnecessary failure points in the cable and connectors.
The unit also includes an XVGA port that isn't routed to the outside of the box, which is itself a fairly defensible decision in something intended to be a network appliance. However, there is no pre-scored punch-out for those who wish to add a video connection permanently to their product, perhaps as a real-time network status display. Note that only one XVGA cable and one SDK CD-ROM were supplied for the two units. This is most likely because this is an OEM product, and an OEM will usually need only one of each as samples and then duplicate them as needed for production.
Particularly vital to a piece of OEM hardware is good documentation. Here again, the Teak falls down. There is no hard-copy documentation, only a CD-ROM full of text files and PDFs (with no PDF reader included).
The CD-ROM contains a slew of documentation for a wide range of models and is not particularly well organized. What's worse, it doesn't actually include some of the most important pieces of documentation on, for example, the motherboard, which you're left to find yourself on-line. Worse yet is that the documentation supplied for the Geode chipset is the preliminary set. The current documentation on the AMD Web site is at revision 2, and there are some significant changes from the preliminary docs. The CD-ROM itself doesn't have a README file, and the package the Teak comes in doesn't have a packing list, so there's no way to be sure that you've gotten everything you're supposed to unless, for example, you bought two or more of them. As an OEM company, that's not a problem, because it's something that's generally covered in the purchase order when the contract is negotiated, but if you're ordering a single box to hack for your own personal project, you're going to have a hard time figuring out whether you got everything you were supposed to. See the sidebar for a packing list I built based on the two boxes I got for this review.
Teak Packing List
SDK CD-ROM full of documentation and drivers.
Six feet of Ethernet cable.
Power cable and power supply (with proper international safety certs).
Two Wi-Fi antennae.
9-pin-to-9-pin RS-232 male-to-male serial interface cable.
XVGA monitor cable to plug straight in to the motherboard.
Four screws, Phillips, presumably for mounting a hard drive.
Unfortunately, the documentation's troubles don't end there.
The block diagram—essential for proper software and embedded system design—is scanned at a very low resolution. Hard to read on the included PDF, it becomes marginally legible when printed out. The block diagram itself is incomplete—the Wi-Fi module isn't included on the generic block diagram, not to mention there's no indication that it's plugged in to the MiniPCI slot. Neither the block diagram, nor the other documentation, indicates the type of Wi-Fi card—we identified it by looking at the labels on the chipset and finding the manufacturer details on the FCC Web site.
There's also the curious matter of J12, a set of pin connectors on the motherboard that do something—what, you may ask? We haven't the foggiest idea. It may be for the video capture hardware, or it may be for the sound chip, or something else. There's no way to tell—it's not in the documentation, and it's not silk screened on the motherboard.
Information on the BIOS—including any place to download updates—is also curiously absent from the documentation. Meanwhile, on the CD-ROM, they do supply an audio driver compatible with the onboard audio chipset, while the location of the pins for accessing and wiring up the speaker/microphone/line-in ports to the audio hardware is curiously absent from all documentation. This is understandable, as this is a network security appliance, not a general-purpose box.
The specs for the box mention a BIOS ROM upgrade utility, but there's no sign of it on the SDK CD-ROM. And then, there's the GeodeROM documentation. AMD doesn't make the GeodeROM available, so why's it there? Checking the AMD Web site, we found out that the GeodeROM documentation is supplied because it contains useful hints on how to make the best use of the chipset.
The two boxes we got had an external label problem as well. The first box was labeled NSM-3018-1, while the second box had a label showing NSM-3018-7. We suspect this is a printer's error on the second label, but there's no way to be sure with what we were provided.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- Stunnel Security for Oracle
- SourceClear Open
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Tech Tip: Really Simple HTTP Server with Python
- Non-Linux FOSS: Caffeine!
- Google's SwiftShader Released
- Doing for User Space What We Did for Kernel Space
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