Free dominions 3 software for linux

Dominion is a multi-playerworld simulation and role-playing game. Each user controls a nation, making economic, political and military decisions for it.

This is a world simulation game developed initially by students at SUNY at Stony Brook, and then by students at Stony Brook and other universities. The intention is to write a game which offers the role playing potential and complexity of relations found in conquer (written by Ed Barlow, then picked up by Adam Bryant). The plan is to
extend the game by offering general descriptions of many features (such as races, magic spells, armies, spirits and technology powers). For example, the races of the world are not limited to 4 hard-coded races, but are described in a file which can be modified at any point in the game by the Game Master. The same goes for army and spirit types.

Dominion is *not* another version of conquer; things work quite differently, and we have *never* looked at the conquer source. Still, we acknowledge this most creative game which gave us our inspiration. In September 1990, the author of conquer version 5 has heard of many of the features of dominion, and has included them in conquer version 5. He has acknowledged that these ideas come from Dominion.

The Game Master is given a nation, but this nation is sort of "fragile", since it has no sectors, and such stuff. We should make it more solid, but meanwhile it is to be used mostly for its [E] command, which allows the Game Master (who logs into the game as "Gamemaster") to change the properties of a sector or of a nation.

Dominion development started in the spring of 1990, when Mark Galassi was running a game of conquer for graduate and undergraduate students at at Stony Brook. After the data file kept crashing, and a whole lot of inconsistencies were discovered, and we found that the source was too complex to be fixed, we decided to write our own replacement. Ed Barlow did a great job with conquer, and it is a great game, but it
was his first C program, and people who added to it kept the endless case statements, and the special cases, and worked on new features rather than re-writing. The original name of Dominion was Stony Brook World (sbw), but it has been named Dominion since version 1.02.

In many ways Dominion was a teaching project intended to teach many Stony Brook undergraduate CS majors to work on a large software development project. Once the project reached a certain size, people from other universities joined in the development.

One goal of dominion is that the ruler of a nation should always have many choices available on how to invest resources, each one presenting strong but distinct advantages. Conquer contains both a good and a bad example of this: you can invest metal in cities, ships or armies. Either way you get advantages, and you have to choose. On the other hand, jewels are really not used for much else than getting magic powers. You can also use them to support monsters, but that is a different order of magnitude, and few players get the monsters. In dominion, there should be several decisions you can make to invest all your resources.

Kevin Hart has been working on the CN code which allows the computer to play various nations. Starting with version 1.05, the computer-played CNs have begun posing a real challenge in the game.

RocksnDiamonds is an arcade style game for Linux, Windows, Mac OS X and DOS in the tradition of:
"Boulder Dash" (C 64)
"Emerald Mine" (Amiga)
"Supaplex" (Amiga/PC)
"Sokoban" (PC)
Main features:
- network multiplayer games (upto 4 players) for Unix platform
- local multiplayer games (upto 4 players) for all supported platforms
- soft scrolling with 50 frames per second
- freely customizable keyboard and joystick support
- stereo sound effects and music
- music modules and fullscreen in SDL version
- contains levels to play Boulder Dash, Emerald Mine and Sokoban
- lots of additional levels available (over 10.000)
- distributed with full source code under the GNU General Public License
- available for Unix (all flavors), DOS and Windows (95/98/NT/2000/XP)
- known to work under BeOS and Mac OS X
- should compile on any platform supporting either X11 or SDL

Sanos is a minimalistic 32-bit x86 OS kernel for Java based server appliances running on standard PC hardware.
This enables you to run java server applications without the need to install a traditional host operating system like Windows or Linux. Only a standard Java HotSpot VM and the sanos kernel are needed.
The kernel was developed as part of an experiment on investigating the feasibility of running java server applications without a traditional operating system only using a simple kernel.
The kernel implements basic operating system services like booting, memory management, thread scheduling, local and remote file systems, TCP/IP networking and DLL loading and linking.
A win32 layer allows the Windows version of the standard HotSpot JVM to run under sanos, essentially providing a JavaOS platform for server applications. This enables you to run java based server applications, like tomcat and jboss, under sanos.
Alternatively, you can use sanos as a small kernel for embedded server applications written in C. Sanos has a fairly standard POSIX based API and an ANSI Standard C library. In this case you dont need the JVM and the win32 wrappers.
Sanos is open source under a BSD style license. Please see the COPYING file for details.
Click on the topics below for further information, or send me an e-mail if you have any questions, comments or problems regarding sanos. Please include the word sanos in the mail to prevent it from being intercepted by my spam filter.
Sanos can be downloaded as either binary or source. All the files in the binary version can be built from the source version, so you do not need the binary version, if you are building sanos from source.
The binary version contains the compiled version of sanos, with files and utilities for making a boot disk.
The source version contains all the source code and build files for building sanos from source. You will need a Microsoft Visual C compiler to build sanos from source.
Enhancements:
- GetLogicalDrives() in kernel32 implemented.
- A bug in cmd_ipconfig() in sh.c prevented proper display of network configuration if no DNS servers was configured. This problem has been fixed. (FGA)
- New -a option added to mkdfs to support file lists with alternative files names. This simplifies configurations with both debug and release builds.
- The Visual Studio wizard can now generate a floppy disk boot image configured for the application.
- Shell prompt can be configured by setting the prompt property in the [shell] section of the os.ini file.
- If command line arguments are given to the shell it now executes the built-in command and exits the shell.
- The floppy motor timeout routine now acquires the floppy mutex before turning off the motor in order to prevent race conditions.
- Advanced Power Management (APM) support implemented. The computer can now be powered off after os shutdown. The mode parameter for exitos() can be used to specify the shutdown mode (halt, reboot, poweroff, debug). A shutdown command has been added to the shell. The power status can be retrieved using /proc/apm.
- Added /proc/cpu for CPU information.
- The raise() function now returns an error if the signal number is invalid.
- Breakpoint traps are now sent to the user mode signal handler. This allows breakpoints to be handled by user mode code.
- Signals now exits the currently executing job with the signal number as exit code. However, if the debug flag in the PEB is set the debugger is entered if an unhandled signal is encountered. The debug flag can be set using the debug command in the shell. The debug flag can be configured using the debug property in the [os] section of os.ini. The default value of the debug flag is 0, unless the system is build in debug configuration.
- readv() and writev() implemented in vfs.
- The kernel log is now implemented by the device driver /dev/klog. The kernel log now support ioctl for waiting for new log entries in the kernel log. The kprintf has been extended to support different log levels.
- The syslog interface has been redesigned in to comply with POSIX. The syslog now supports logging to a syslog server by setting the loghost property in the [os] section of os.ini.
- New klog daemon to read entries from the kernel log (/dev/klog) and add them to the system log.
- The sockaddr and sockaddr_in structures has been change to conform to winsock definitions.
- The sleep() function has been renamed to msleep(). A new POSIX conformant sleep function has been added to unistd.h.
- Added sys/time.h header file. Also added tzp parameter to gettimeofday() for POSIX compliance.
- New simple text editor utility (edit.exe) added.
- The syserror() function has been moved from libc.lib to the os.dll as an exported os api call.
- readline() now uses stdin and stdout for input and output.
- Bug in iomux fixed. Now a monitored event signals the iomux and not the associated object.
- Implemented popen() and pclose(). Also added a P_SUSPEND parameter to spawn() to allow new jobs to be started suspended.
- The kernel version information is now kept in a version resource in krnl.dll. The version information is retrieved using the new module version information functions in verinfo.c.
- The build type can now be controlled by compile time switches. The kernel version can be displayed in the Windows Explorer by viewing Properties for krnl.dll and selecting the Version tab.
- User management added to kernel. Each thread is now assigned to a user and a group. A thread has both a real and an effective user and group owner. The {get|set}[e]{uid|gid}() functions can be used to change the effective and real user and group for a thread. When a new thread is created the effective user and group are inherited from the creator thread.
- Added functions to query /etc/passwd and /etc/group files.
- New whoami, id, chmod, and chown commands added to shell. The format of the output from ls has been changed to display the file permission info.
- New file system version for DFS. The new version supports user and group owner for files and directories as well as permission bits. The new DFS version also supports files larger than 2GB. The fchown() and chown() functions has been added to vfs.
- DES-based crypt() implementation added.
- The spawn() function now computes the pgm parameter from the cmdline parameter if the pgm parameter is NULL. The initpgm and initargs properties in the [os] section of /etc/os.ini has been replaced with a single property named init. The default for init has been changed to /bin/sh.
- The behavour of the initial application has been changed. Previously the os shut down after the initial application exited. Now the initial application is executed again if it exits.
- Telnet daemon moved from the shell to separate server (telnetd.exe). The new telnet daemon has a more robust handling of the telnet protocol. The telnet daemon invokes the new login utlity in order to log on user.
- FTP daemon implemented.

LinCAN is a Linux kernel module that implements a CAN driver capable of working with multiple cards, even with different chips and IO methods. Each communication object can be accessed from multiple applications concurrently.
It supports RT-Linux, 2.2, 2.4, and 2.6 with fully implemented select, poll, fasync, O_NONBLOCK, and O_SYNC semantics and multithreaded read/write capabilities. It works with the common Intel i82527, Philips 82c200, and Philips SJA1000 (in standard and PeliCAN mode) CAN controllers.
LinCAN project is part of a set of CAN/CANopen related components developed as part of OCERA framework.
Enhancements:
- Some more fixes were made in SJA1000 bus-off recovery.
- The i82527 IRQ stuck problem was fixed.
- The module was updated and tested up to kernel version 2.6.17 (rc4).
- Minimal chip information was added in /proc/can.
- Support for NSI CAN PCI was contributed.

ntop is a network traffic probe that shows the network usage, similar to what the popular top Unix command does.
The project is based on libpcap and it has been written in a portable way in order to virtually run on every Unix platform and on Win32 as well.
ntop users can use a a web browser (e.g. netscape) to navigate through ntop (that acts as a web server) traffic information and get a dump of the network status.
In the latter case, ntop can be seen as a simple RMON-like agent with an embedded web interface. The use of:
a web interface
limited configuration and administration via the web interface
reduced CPU and memory usage (they vary according to network size and traffic)
make ntop easy to use and suitable for monitoring various kind of networks.
Main features:
- Sort network traffic according to many protocols
- Show network traffic sorted according to various criteria
- Display traffic statistics
- Store on disk persistent traffic statistics in RRD format
- Identify the indentity (e.g. email address) of computer users
- Passively (i.e. withou sending probe packets) identify the host OS
- Show IP traffic distribution among the various protocols
- Analyse IP traffic and sort it according to the source/destination
- Display IP Traffic Subnet matrix (whos talking to who?)
- Report IP protocol usage sorted by protocol type
- Act as a NetFlow/sFlow collector for flows generated by routers (e.g. Cisco and Juniper) or switches (e.g. Foundry Networks)
- Produce RMON-like network traffic statistics
Additional features of "ntop":
- Network Flows
- Local Traffic Analysis
- Multithread and MP (MultiProcessor) support on both Unix and Win32
- Perl/PHP/Python lightweight API for accessing ntop from remote
- Support of both NetFlow andsFlow as flow collector. ntop can collect simultaneously from multiple probes.
- Traffic statistics are saved into RRD databases for long-run traffic analysis.
- Internet Domain, AS (Autonomous Systems), VLAN (Virtual LAN) Statistics
- Network assets discovery and categorization according to their OS and users
- Protocol decoders for most of known P2P (Peer to Peer) protocols
- Advanced per user HTTP password protection with encrypted passwords
- RRD support for persistently storing per-host traffic information
- Passive remote host fingerprint (Courtesy of ettercap)
- HTTPS (Secure HTTP via OpenSSL)
- Virtual/multiple network interfaces support
- Graphical Charts (via gdchart)
- WAP support

NodeMon is a visualization tool for monitoring system resource utilization. It allows distributed resource monitoring via the Growler software infrastructure.

It is modular, with existing modules for monitoring of CPU, memory, network, and numalink activity. Its most notable feature is its composition of large amounts of statistics into a single graphical window. This project was originally designed for monitoring NASAs Columbia supercomputer.

OpenLaszlo is the premier open-source platform for rich internet applications.

OpenLaszlo is an open source platform for creating zero-install web applications with the user interface capabilities of desktop client software.

OpenLaszlo programs are written in XML and JavaScript and transparently compiled to Flash and soon DHTML. The OpenLaszlo APIs provide animation, layout, data binding, server communication, and declarative UI. An OpenLaszlo application can be as short as a single source file, or factored into multiple files that define reusable classes and libraries.

OpenLaszlo is write once run everywhere. An OpenLaszlo application developed on one machine will run on all leading Web browsers on all leading desktop operating systems.

Cinematic user experience
Applications developed on OpenLaszlo provide a dramatically improved online user experience featuring advanced interfaces delivered on a single Web page. By bringing true application behavior to the Web, OpenLaszlo makes a new generation of online communications, commerce and content services viable for the first time.

imageRapid XML development approach
OpenLaszlo applications are written in LZX, a standards-driven XML and JavaScript description language that enables a declarative, text-based development process. LZX supports rapid prototyping, collaborative software development and long term code maintenance.

imageScalable deployment architecture
Depending on requirements, OpenLaszlo applications can be deployed either SOLO (Standalone OpenLaszlo Output) or from the OpenLaszlo Server. SOLO deployment supports most use cases and works from any HTTP Web server. OpenLaszlo Server deployment supports additional data integration options, persistent connections and run-time media transcoding. The OpenLaszlo server is Java-based and works with leading J2EE application servers and Java Servlet Containers. OpenLaszlos standards-based architecture delivers exceptional reliability and scalability, proven in deployments serving millions of users to date.

Benefits

Develop standards-based rich Internet Applications that support any web browser with a single code base in XML and JavaScript.

Deploy them from any HTTP Web server in SOLO mode, or from a J2EE application server or Java servlet container running the OpenLaszlo Server under Linux, UNIX, Windows or Mac OS X.

Display them in any Web browser enabled with the Flash 6 Player or above, reaching 96% of all Web-enabled desktops.