Free first signs of pregnancy software for linux

Rigs of Rods is a truck simulator based on soft body physics.
Rigs of Rods is a simulation game based on a custom advanced soft body physics engine.
In a vast open world, you can drive trucks, control cranes and fly airplanes. The chassis and wheels deform according to the stress they bear, and crashes are interesting to see too!
The linux version is still a release candidate under compatibility testing.
The main issue is that it is compiled with a GCC 4.1.1 compiler, and there are many incompatible C++ ABI out there. So it will probably work on a gcc 4.1.1 system, and break on a gcc 3.4 or 3.6 system. I dont know if there is an easy fix to that. Be aware that upgrading your gcc may break badly your system if not done correctly, so do it at your own risk.
Also, if you see the config box, but the game crashes, check the sanity of your GLX system first (test with another GLX program) because it breaks easily. It works with NVidia drivers, but I have not tested the ATI ones.
Read the README.LINUX file for more important informations.
Enhancements:
- Boats, with a small wahoo, a Class 1 speedboat contributed by cdquicksilver, and a very large high sea tug, the Smit Rotterdam, that has a rollable platform.
- A new terrain, called "island", that is still under construction but that will soon replace the two classic RoR terrains, because they are not realistic islands.
- Infinite sea with waves. Take the Smit and sail far from the island: you will encounter high swells offshore. You can even configure the wave fields (see the datawavefield.cfg file).
- A separate configurator program. Now you must start the RoRconfig program first, to choose your configuration options, save them, then start RoR.
- Serious bugfixing: camera shaking has been dramatically reduced, and the "crash on plane crash" problem is mostly eliminated.
- Addition of the Challenger car contributed by hemicuda.

FIRST DiskImager is an advanced, full-featured GUI disk image acquisition tool.

It was designed for forensic disk image inspection. Developed using C++ and QT. This is our 1st attempt to create an acquisition software to meet the NIST standards.

******** WARNING !!! USE THIS SOFTWARE AT YOUR OWN RISK!!! **************

Ive tested and used the software and it works for me, but there is no guarantee that it will work for you. You can very easily DESTROY DATA IRRECOVERABLY by using this software. Do not even attempt using this software unless you are VERY FAMILIAR with the process of imaging hard drives and other media. While this program is intended to make the imaging
process more convenient, it cannot THINK for you. If you mix up the source and destination targets and accidentally overwrite the original evidence, there is nothing I (or anyone else) can do for you.

DO NOT USE THIS SOFTWARE FOR ACTUAL PRODUCTION OR CASE WORK UNTIL YOU HAVE THOUROUGHLY TESTED IT AND HAVE SATISFIED YOURSELF THAT IT DOES WHAT YOU WANT IT TO DO. I WILL NOT BE RESPONSIBLE FOR UNEXPECTED RESULTS OBTAINED FROM THE USE OF THIS SOFTWARE WHETHER THEY ARE THE RESULT OF PROGRAM BUGS, USER ERROR, HARDWARE FAILURES, OR ACTS OF GOD. AGAIN, IF YOU USE THIS SOFTWARE YOU DO SO AT YOUR OWN RISK AND ASSUME ALL RESPONSIBILITY FOR THE RESULTS.
***************************************************************************

Secret of Eternia project is a 2D RPG using ClanLib.
The eaisest way to get started is to use an example map from the game itself. Open up (File-Open) the first map in the maps/ folder (maps/1.fmp). You will notice that the map looks exactly like the first screen of the game demo!
You will notice the screen is divided into 2 main sections. The larger section is the preview of the map you are working on. The left side menu is a listing of all avaliable blocks that you currently have in the map. You can click on a block to set it as your current brush. This is similar to choosing a paint color in a paint program. Once you select a block, you can then edit the map by clicking in the map area. This is the generic way to edit the map.
Play around with this map to create some different landscapes and such using many blocks. You can even save the map and start up SoE to see your changes! (Make sure you have a backup of the original map, or you will have to download the game again).
Enhancements:
- Bug fixes! See the forum for detailed information.
- Lua support is added in. (see docs/ for how to use this)
- Lighting effects are here!
- Fully Working Windows Support

Enterprise Sign On Engine (ESOE) is an advanced system which allows an enterprise to meet its individual goals for integrated identity management, federation, single sign on, authorization and accountability for resource access in a very extensible manner.
The ESOE is built using the OASIS SAML 2.0 specification, and the ESOEs powerful authorization engine is built around a reduced version of the OASIS XACML 2.0 standard which we have called Lightweight eXtensible Authorization Control Markup Language or "LXACML".
The ESOE can integrate identity from unlimited repositories, automatically create sessions for users whom are logged into Active Directory (true single sign on), provide for centralized authorization policy management and natively federate with technologies such as Shibboleth and OpenID.
We hope youll find the ESOE a good choice for your needs amongst the wide variety of SSO solutions that are available, both from commercial providers and other open source projects. Of course if youre already using an SSO solution, there is a pretty good chance the ESOE can interact with it, allowing you to use the enhanced capabilities of the ESOE without needing to replace everything you already have.
Being heavily standards based, all your existing identity infrastructure such as LDAP compliant directories, databases and even flat files are only a plugin away. The ESOE is designed to fit around your environment, not have your environment change to fit it.
Were calling the current release an Alpha and some of the service providers, tools and documentation are still coming up to full completion. Nonetheless, we hope youll have a look around at what the ESOE can do for your enterprise and contribute back anything you can to help us build a strong community of users for the future.
Enhancements:
- Many bugfixes have gone into this release specifically relating to MySQL deployments.
- New features for this release are integrators for Confluence, Jira, and Blackboard.

Signs is a tool for logic synthesis and gate level simulation. Signss project main features include synthesis of RTL-style VHDL circuit descriptions and a dynamic graphical netlist viewer.
Supported formats include VHDL, ISCAS, and limited support for BLIF, Verilog, and EDIF netlists. Various true value and fault simulators and a combinational ATPG are included for circuit testing.
Aside from GUI mode, Signs has a pure command line mode and is fully scriptable in JavaScript and Ruby.
Main features:
- Written in Java, therefore platform-independent
- Aims to be VHDL93 compliant, at the moment a VHDL Subset is supported
- (Limited) support for non-synthesizable VHDL code, useful for testbenches
- Synthesis of RTL-style sequential VHDL process descriptions according to IEEE Std 1076.6
- Dynamic graphical netlist viewer supporting annotations (signal/gate names, signal values provided by simulators, faults)
- VHDL netlist output to file
- Input and output of netlists in ISCAS benchmark format
- Gate level true value simulators: event-based (any circuit), bit-parallel (combinational circuits only)
- Fault simulators: PPSFP, simple single faultsim
- Input and output of pattern lists in WGL format
- ATPG for combinational circuits: Implication-Graph based, PODEM
- Limited support for Verilog and EDIF netlists
- Fully scriptable in Rhino: JavaScript for Java and JRuby
- Pure command-line mode available besides GUI mode
- Integrated environment including source code and netlist structure tree views, build system, compilers and editors with syntax highlighting
Enhancements:
- While the release focus is clearly on bugfixes, there are also some feature improvements, such as enhanced test bench support and improved netlist and simulator views.
- The VHDL compiler has support for subprograms now and elaboration of big designs is much faster because of improved context handling.
- Internally, the intermediate representation layer was cleaned up, so intermediate objects form a proper tree now.

Tuxpaint Stamps for Australian Schools is a collection of stamps and other resources for Tuxpaint for use in Australian schools. Tuxpaint Stamps for Australian Schools includes Australian coins, bank notes, signs, animals, plants, and state flags.
Installation Instructions:
- Close Tuxpaint
- Locate your tuxpaint stamps directory
- On Unix/Linux this will be something like /usr/share/tuxpaint/stamps
- On Windows it will be something like C:Program FilesTuxpaintstamps
- Extract the contents of the archive (tuxpaint-au-stamps-x.y.z.tar.gz) to the stamps directory
- Run Tuxpaint and select the stamps tool
Enhancements:
- The software was split into two packages.

Invasores project was first designed as a proof of concept of which language would be faster to develop games.

sign is a file signing and signature verification utility. Its main purpose is to be a simple and convenient extension to a tar/gz/bzip2 line of tools to check file integrity and authenticity. Its small and simple, it does just one thing and hopefully does it well.

I needed a tool to digitally sign a bunch of .tar.gz and to allow recepients of the files to easily check, unzip, untar and start enjoying the content as quickly and painlessly as possible.

There are OpenSSL, GnuPG, PGP and others and they are of course perfectly capable of file signing. OpenSSL is probably the most widely spread one and best suited for the role of being a universal signing utility. However the state of affairs is such that OpenSSL as an application is not really used for anything more than generating tarball MD5 hashes. The other packages are plain big and complex for a simple task of file integrity checking. Its like getting a professional sound editing suite instead of a dead-simple .mp3 player. The larger crypto-packages also tend to lack modularity in a sense that to get file signing working I would need to configure a handful of core, but otherwise unrelated settings first. Besides if I am not going to use anything but a signing code, the rest will be sitting there collecting dust, creating untrivial shared libraries dependencies and a general feeling of a wasted disk space.

First of all, sign is a file processing tool, it reads from the files (including stdin) and writes to the files (including stdout). It can be used to attach signatures to the files or to verify and/or strip them.

Between signing and verifying latter will account for a bulk of usage. When checking the signature, sign will check for both integrity and authenticity of the file. An integrity check is done by validating SHA-1 hash embedded into the signature, and an authenticity is ensured by checking signers credentials against a trusted list.

sign adopts OpenSSH-style authentication model, where the trust hierarchy is flat (no certificates), an authentication is done with public keys and the list of trusted keys is grown gradually on as-needed basis.

Every trusted key is associated with a file name prefix called the title. The key can be trusted for signing files, whose name start with keys title. The same key may be associated with more than one title, but not vice versa.

The signature is appended at the end of the file and it carries three bits of information - the title, the public key of the signer and the hash of all preceeding data encrypted with signers private key. The verification is performed as follows:

The filename is checked to start with a title
The hash is decrypted using the public key
The hash is compared to the locally computed value (this ensures integrity)
The title is looked up locally; if its known and associated public key is the same as in the signature, the file is deemed authentic.
Otherwise if the title is known, but the key is different, the file is considered to be signed by untrusted, impersonating party and the check fails.
And lastly, if the title is unknown, the authenticity of the file cannot be established. The user is provided with public key fingerprint, which should be manually authenticated. Then the title and the key are added to the trusted list; and subsequent signatures from the this signer for this particular title will be cleared automatically.

In order to sign files, the signing keypair must first be generated. The keypair is maintained on per-user basis and can be created by running sign with a special command-line flag. The signing process itself is as follows (give or take insignificant details):

Run the filename through a list of owned titles and find the best match. Alternately accept explicit title from the user using one of the command-line flags.
Attach the title, attach public signing key
Compute the hash, encrypt it with private signing key
Attach encrypted hash.

For details on command-line syntax and other operating parameters, please refer to a man page; an online version is here.