Linux in Camouflage
As the Army's demand for real-time, battle-command information increased, computer systems became more complex, expensive and unwieldy. To counter the proliferation of single-use systems, the Army's Battle Command Laboratory (http://cacfs.army.mil/) at Fort Leavenworth entered into a rapid prototyping agreement with Mystech Associates to design a new Maneuver Control System for the Army.
Maneuver Control System/Phoenix (MCS/P) was approved by the Department of the Army in November 1995 to be issued to Army units for training and feedback. While not the final answer, it is the best system available for providing interoperation between the Army's “command and control” computer systems. In January 1996, MCS/P was used successfully by the 4th Infantry Division and III Corps in a Battle Command Training Program Warfighter exercise. MCS/P is currently in use in Bosnia and other theaters around the world.
MCS/P and its sister intelligence system, ASAS Warlord Notebook, share the same underlying code and provide the military with the applications shown in the “Applications” box.
Originally developed to run on Sun SPARC 20s, MCS/P and Warlord Notebook have been successfully ported to Linux systems by Mystech. Porting these applications to Linux provided a cost-effective solution to employing these systems on a large scale. The tactical version (hardened and ruggardized) of the SPARC 20 costs the U.S. taxpayer approximately $48,000.00 per machine; the non-tactical or commercial system about $18,000.00. The commercial Pentium 166 machines running the Linux port cost approximately $3,000.
The National Guard Bureau realized the benefits and importance of training its commanders and their battle staffs to operate effectively and efficiently in this information-rich environment. The Leader Development Center (LDC) was given the task of developing and implementing procedures to infuse these systems and technologies into the National Guard. In September 1996, the LDC established a training site at its Fort Leavenworth facility and issued Linux systems to the National Guard's 34th and 38th Divisions. These two divisions will use Phoenix and Warlord Notebook during their 1997 Battle Command Training Program Warfighter exercises at the LDC.
Phoenix and Warlord Notebook provide National Guard commanders at multiple echelons with enhanced situational awareness and a relevant common picture of the battlefield overlaid on digital maps. These two systems provide the commander near-real-time combat information over battlefield communications from their battle staffs, subordinate commanders and intelligence assets.
The software systems are comprised of government owned, GNU licensed and other freely distributed software. The current X Window System is XFree86. To a Linux purist the file structure is wrong. Since the official platform to run these applications is the tactical SPARC, the file structure mirrors that of the SPARC. While confusing at first, this change eliminates the problems caused by operating on multiple systems with different file-system structures and simplifies file transfers.
Each computer has both Phoenix and Warlord Notebook installed, and is its own mail host and web server. The user ID of the individual using the system determines which application system is started.
Military operations are map and graphic intensive. Instead of paper maps, digital map products from the National Imagery and Mapping Agency (http://www.nima.mil/) are used. To reduce the bandwidth required for communication, full digital maps reside on each system. The only map or graphic material actually transmitted are the geo-referenced graphics. Geo-referencing allows the re-scaling of maps and graphics without loss of clarity or the danger of graphics being out of position. (See Figure 2)
Information on friendly and enemy unit activities and locations is loaded into the system at the first point of observation or occurrence and is then sent throughout the network. Once entered, the data does not have to be re-entered anywhere along the network. The user is unaware that the majority of information is sent using normal e-mail. He clicks on the operation that he needs to be accomplished, e.g., send updated unit locations, and the system queries the appropriate data bases, prepares the message and sends it.
Operations orders are centered around the maps and maneuver graphics. Now, instead of taking the graphics, converting them to words, transmitting the words which are then converted back into graphics on the receiving end, the information is sent as graphics with a minimum of words. An ingenious use of HTML and CGI provides the capability to build complex operations orders with full graphics and map references. Then, with CGI, these orders are available to be either pushed or pulled throughout the network.
A collaborative white board is built in. This provides the commander with a rapid means to clarify his points or make last-minute changes.
One of the most perplexing problems in data entry on tactical systems used to be that the user had to know a myriad of archaic formats and had to enter those formats as text. Phoenix and Warlord Notebook uses simple fill-in-the-blank forms and lets the computer figure out where the “/” and “.” characters should be placed. (See Figure 3 and Listing 1.)
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!
- Paranoid Penguin - Building a Secure Squid Web Proxy, Part IV
- SUSE LLC's SUSE Manager
- Google's SwiftShader Released
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- 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