Jagged Alliance 2 for Linux
Jagged Alliance 2 requires a fairly minimal hardware setup to run. Tribsoft recommends only a PII 233MHz with 32MB RAM, a 4X CD-ROM and 400MB of free hard disk space. Since nothing about JA2 requires 3-D acceleration, pretty much any card that will run at least XFree86 3.3.x at 640 × 480 or higher should work just fine. An OSS-compatible sound card is required, of course, and Tribsoft also suggests a version 2.2 Linux kernel (or greater) as well as glibc 2.1 or higher. The game played like a dream on both of the 700MHz and 500MHz systems I tested it on (GeForce/Debian woody and G400/VA-enhanced Red Hat, respectively). The installation footprint can vary from 305MB (the base installation) to over 800MB (if you want to put all the maps and speech files on your hard disk) and can be done with either a shell script or a nice-looking graphical installer.
This is really a great game. At first, I admit, I was skeptical about this title, owing mainly to its relative age in the gaming market, low-tech graphics and seemingly overly complex controls, but once I got to know JA2, I really began to understand just how cool this game is and why Tribsoft chose to port it. It's one of those games that you can play a hundred times and have a hundred different games and still want to try something different the next time. There's an attractiveness to this game that's hard to define; maybe it's the profound individuality of the mercs themselves, the personal touches from all the dialogues of the NPCs, the choose-your-own-adventure feel or the ever-so-smooth transitions between strategy, tactics, real time and turn-based action modes. Either way, JA2 is a game that you can play for hours on end and still want more. Highly recommended for anyone not afraid of a little complexity in their games.
|September 2015 Issue of Linux Journal: HOW-TOs||Sep 01, 2015|
|September 2015 Video Preview||Sep 01, 2015|
|Using tshark to Watch and Inspect Network Traffic||Aug 31, 2015|
|Where's That Pesky Hidden Word?||Aug 28, 2015|
|A Project to Guarantee Better Security for Open-Source Projects||Aug 27, 2015|
|Concerning Containers' Connections: on Docker Networking||Aug 26, 2015|
- Optimization in GCC
- Using tshark to Watch and Inspect Network Traffic
- September 2015 Issue of Linux Journal: HOW-TOs
- Problems with Ubuntu's Software Center and How Canonical Plans to Fix Them
- Concerning Containers' Connections: on Docker Networking
- A Project to Guarantee Better Security for Open-Source Projects
- Firefox Security Exploit Targets Linux Users and Web Developers
- Where's That Pesky Hidden Word?
- My Network Go-Bag
- Doing Astronomy with Python