Hamming It Up On Linux
The first house has something very different about it, seen even without the binoculars. You can see a 50-foot tower looming high into the sky. On the structure are scores of antennas in every size and shape imaginable. As you “peer” into the den of the house, you see more electronic equipment than you would expect to find at the local radio station. There are dials, lights, LEDs, and meters of every kind. There are the sounds of Morse code, static, and eerie-sounding human (human?) voices. The man at the equipment has a microphone in front of him, and in his right hand there is a telegraph operator's key.
Now, moving to the second house, we see a typical home, like you'd expect in Anytown, USA. Nothing unusual as we approach it. So get out the binoculars! (Come on, get into the shadows. Someone will see us!)
In the den of this home, we find an ordinary-looking man sitting at his personal computer. His eyes seem a bit bleary, but he seems to be enjoying whatever it is that he is doing. Looking closer, you can see that the operating system is obviously Linux, as he swaps virtual consoles at the speed of light. But then he stops on one VC which seems to be an IRC-type chat group, but instead of “handles”, each VC is identified by a cryptic series of letters and numbers...
Okay, put the binoculars down. What do these two men have in common? They are both amateur radio operators. And amateurs have been migrating to Linux in remarkable numbers. In this article, I'll try to give the non-amateur a feel for why this is occurring, from an insider's viewpoint (yes, I'm one of them: KO4KS is my amateur radio callsign).
Without getting into the nitty-gritty details of it, the countries of the world cooperate together to provide radio spectrum for use by licensed operators for experimentation, public service, and just plain fun!
Amateurs have a wide variety of radio-related ways to enjoy their hobby. There is the traditional Morse code, shortwave, as well as local voice communications. In addition, among others, there are satellite communications, participation with the space program, and something called packet radio.
Most of you have probably seen e-mail addresses in the “ampr.org” domain. These are addresses of amateur radio operators, using packet radio. But how did they get on the Internet? Don't get ahead of me....
Packet radio is described by some as Ethernet over radio (though Ethernet used to be described as packet radio over wire). Anything you can do over Ethernet can be done over packet. Packet operators and programmers have been highly involved in many Internet RFCs as they have found ways around the problems encountered in using radio in this manner.
Packet radio uses a variation of the X.25 protocol called AX.25 (Amateur X.25). Their radios are connected to their computers with a little packet modem.
Initially, the “killer app” of packet radio was the Packet BBS (PBBS). PBBSs are pretty crude by today's BBS standards, but they pass messages internationally by means of thousands of individually owned radio sites that relay the mail, hop by hop along the way. Some packet PBBSs have HF (“High Frequency”--which, paradoxically, is at the very low end of the frequencies used for packet radio) ports for passing the mail over longer hops, but most hops are only a few miles each.
Then, several years ago, Phil Karn/KA9Q wrote a program called NET, to incorporate AX25 and TCP/IP together on computers running MS-DOS. As time progressed, NET became NOS (Network Operating System), which was now a multi-threaded application allowing multiple incoming and outgoing sessions. I am told that some commercial manufacturers have licensed the KA9Q code as a base for their development, and many of the new and modified protocols have made their way into commercial wireless TCP/IP networks.
Phil made his code available freely to amateurs and for educational purposes and even has allowed variations to spring up. There are many “xNOSs”, such as WNOS, JNOS, PMNOS, etc. and others that I'm sure I missed. I'm a little partial to Tampa NOS (TNOS), since I am the one who has developed this variation.
This interest in TCP/IP leads very naturally to Linux, but even more so when you consider the limitations of a program like xNOS under MSDOS. Good ol' DOS doesn't have a linear memory map, TCP/IP or multitasking built in. And it does have the 640K conventional memory barrier. It also requires dedicating a computer to xNOS under DOS.
Packet Radio Meets Linux
Linux is a good move for xNOS, since the DOS-related restrictions are gone. A couple of xNOSs have already been ported to Linux, including TNOS. Those interested can find it at ftp.lantz.com:/tnos/current/linux. For Web slingers, try www.lantz.com.
NOS under Linux is still a large program, with all of the same features as the DOS version, including its own TCP/IP stack. You can connect TNOS to the Linux TCP/IP stack by means of a ptty SLIP or PPP link.
Amateur Radio TCP/IP is passed over the real Internet by Amateur gateways. These gateways exist both on the Internet and on the local packet network. Other non-gateway Amateur packet stations can pass packets through the gateway to Amateur stations on the other side of distant gateways. This is done by encapsulating the 44.xx.xx.xx addresses (addresses assigned to the ampr.org domain) into “real” Internet addresses for passing through the backbones.
|Speed Up Your Web Site with Varnish||Jun 19, 2013|
|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|
- Containers—Not Virtual Machines—Are the Future Cloud
- Non-Linux FOSS: libnotify, OS X Style
- Linux Systems Administrator
- Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer
- Validate an E-Mail Address with PHP, the Right Way
- Technical Support Rep
- Senior Perl Developer
- UX Designer
- 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?