by David Bandel
Next to adventure, this game or a variation of it has to be about the oldest computer game. I remember playing a game like this years ago in which two artillery guns lobbed crude-looking bombs at each other. But even before that, in the days when I was using punched paper tape and an acoustic 75-baud modem to connect to a mainframe, I remember playing a game where you input gravity and wind, then set angle and round velocity and tried to hit a computer gun before it hit you. Although light-years beyond either of those primitive games, Atanks is basically the same, only with more and better weapons and shields. Requires: liballeg, libpthread, libXext, libX11, libdl, libstdc++, libm, libgcc_s and glibc.
by Zach Brown
Bryan O'Sullivan has produced Netplug, a dæmon that monitors whether network cables are plugged in and responds by bringing up or shutting down the system's network connection. This is useful for laptops and other systems that move around a lot or that are part of a Beowulf or other cluster. Netplug performs a similar task to the existing ifplugd Project by Lennart Poettering and others, and there may be some movement toward integrating the two projects.
The /proc/kcore interface to system memory may be going away in 2.6 because of the difficulty in maintaining it across the range of architectures and even across multiple versions of a single architecture. Linus Torvalds feels that few people actually use the interface, judging from the lack of complaints whenever it breaks; he believes it may be more trouble than it's worth. It turns out, however, that some developers do use the interface for debugging purposes, although they all agree a much better solution would be to include a proper debugger in the kernel itself. Linus always has been reluctant to do this, because he feels it lowers the quality of developers' debugging efforts.
Several developers have lodged complaints with Linus Torvalds, because he occasionally modifies changelog entries for patches that already have been accepted into the BitKeeper repository. Some developers call this censorship, some say it could lead to legal hassles, and some say it avoids proper version control because the history of the changelog entry is lost. But Linus feels it is good practice to make sure all changelog entries are well formed and accurately describe their corresponding patches. And, it was he who asked Larry McVoy to add the bk comment command, which easily allows such modifications.
NFS behaves a bit differently in 2.6 from the way it behaved in 2.4, resulting in a true incompatibility between the two stable series. The problem seems to boil down to a #define NFSEXP_CROSSMNT expression that always had a slightly inaccurate meaning, one that was corrected in the 2.6-test kernels. Changing it back would mean re-introducing the inaccuracy, so it looks as though the incompatibility will stick around. The incompatibility occurs when third-party code includes the header file containing the affected #define. A simple workaround exists to fix all affected source code.
Junio C. Hamano brought Phillip Lougher's SquashFS compressed filesystem code from 2.4 up to the 2.6-test tree. SquashFS appears to be the most promising compressed filesystem currently available for Linux, although it still provides only one-time write access; thereafter only read access is available. Full read-write access may be added in the future, however. Meanwhile, its predecessor, CramFS, is looking for another maintainer. Daniel Quinlan remains the official maintainer, but he would prefer to step down if a suitable replacement can be found.
by David Bandel
Want to study while you're working at your computer? This program puts flash cards up at predetermined intervals so you can practice while you're waiting for downloads or browsing the Web. Making new cards does require knowledge of LaTeX, but you can follow the example cards. Requires: libXm, libXpm, libXext, libXt, libSM, libICE, libX11, libasymptopia, libm, libstdc++, glibc, libgcc_s, libXp, libdl, libtiff, libpng12, libjpeg, libz and latex.
Practical Task Scheduling Deployment
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.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- Stunnel Security for Oracle
- The Firebird Project's Firebird Relational Database
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Google's SwiftShader Released
- SuperTuxKart 0.9.2 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