The first terminal and console access server to use Linux as the embedded OS.
The TS2000 is a terminal and console access server that can be used by ISPs, ASPs and e-retailers to remotely and securely manage serial console ports in server farms. As a terminal server, the TS2000 connects local or remote clients to the Ethernet LAN, allowing both ISPs and corporate remote-access applications to use serial lines and analog modems. As a console access server it connects to the console ports of servers and networking equipment and allows the system administrator to remotely and securely monitor and manage servers.
Features include RADIUS socket authentication, direct Telnet to serial ports, secure shell connections (SSH), IP packet filtering and RFC2217 support. The TS2000 supports up to 32 RS-232 serial ports in 1U of rack space.
Applications include console port management, dialup remote access, industrial/commercial automation and Ethernet-attached serial board replacement.
Manufacturer: Cyclades Corporation
Suggested Retail Price: $2,741 US
Newest member of the DIL/NetPC family.
SSV Embedded Systems introduced the ADNP/1486, a small PC/AT-based embeddable single-board computer module that plugs into a standard 128-pin Quad-in-Line (QIL) socket. The miniature PC comes with embedded Linux pre-installed in Flash memory and includes a full TCP/IP stack, a Telnet server for remote login, an FTP server and an embedded web server with CGI.
Based on a 3-bit, low-power AMD 486SX processor with 100MHz, the ADNP/1486 provides a complete embedded-PC/AT architecture, plus 16MB of DRAM and 4MB of Flash. Peripheral functions include a COM1 serial port, 20 digital I/O lines and a 16-bit ISA expansion bus interface with programmable chip selects for connecting external logic and devices via the 128-pin QIL socket interface.
Manufacturer: SSV Embedded Systems
Suggested Retail Price: $225 US in quantities of 1,000
Board functions in industrial temperature range of -40° to 85° C.
WinSystems has made available the LPM-TX STD Bus single-board computer, an industrial-grade product based on the Intel Tillamook Pentium processor. The SBC is based on x86 processors and supports PC-compatible software, has long-term availability and offers extended termperature operation. It provides a migration path for STD Bus systems while maintaining hardware, I/O and software compatibility over a full industrial temperature range. Designed for systems that need a small format board that is PC-compatible, it is targeted at embedded and industrial application.
The LPM-TX operates at a system clock of 166MHz and includes 16KB of code and 16KB of data cache, plus a floating-point processor for math-intensive applications. It comes with either 32MB or 64MB of surface mounted synchronous DRAM, and the SDRAM is soldered directly to the printed circuit board to protect against shock and vibration. An onboard 32-pin socket supports up to a 288MB M-Systems Disk-On-Chip Flash memory device for use as a solid-state disk. The Intel 430TX PCI chip set contains core logic to provide PC-compatibility for the I/O and bus interface, including the keyboard controller, 16-channel interrupt controller and real-time clock.
Onboard peripherals include seven DMA controllers, three 16-bit counter/timers, two interrupt controllers, keyboard controller, speaker port and battery-backed, real-time clock. Two independent serial channels, each with RS-232 and optional RS-422/485 levels, USB port, LPT interface and a mouse port are also included, all on a single 4.5" × 7.0" STD Bus board.
Manufacturer: WinSystems, Inc.
Model: LPM-TX STD Bus SBC
Suggested Retail Price: $995 US with 32MB SDRAM
|Designing Electronics with Linux||May 22, 2013|
|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|
- RSS Feeds
- 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?
- Drupal Is a Framework: Why Everyone Needs to Understand This
- Validate an E-Mail Address with PHP, the Right Way
- What's the tweeting protocol?
- Tech Tip: Really Simple HTTP Server with Python
- Kernel Problem
2 hours 10 sec ago
- BASH script to log IPs on public web server
6 hours 27 min ago
10 hours 2 min ago
- Reply to comment | Linux Journal
10 hours 35 min ago
- All the articles you talked
12 hours 58 min ago
- All the articles you talked
13 hours 2 min ago
- All the articles you talked
13 hours 3 min ago
17 hours 28 min ago
- Keeping track of IP address
19 hours 19 min ago
- Roll your own dynamic dns
1 day 32 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?