Free 2.2 turbo software for linux

Xinity project is a powerful web content management system (CMS).
Xinity is a powerful web content management system (CMS). You can build complex web sites with content edited and maintained by non-programmers. It is user-friendy because it eliminates the flexibility gap: in common CM Systems the editor loses the more flexibility the more the programmer gains and vice versa.
In Xinity the programmer has the power to decide how much flexibility the editor has. There are no limitations given by the system.
The editor edits his content in WYSIWYG, and there is no need to battle with or system-specific variables. Xinity is a highly scalable system with a lot of customization work to do with each installtion, and is not suitable for a quick test run.
On the other hand there is a generic site architecture that comes with the base distribution, so you can set up you own Xinity web site in 30 minutes.
Enhancements:
- revise Exception-Handling and inform Client properly [TOBIAS done 11/4]
- inform client if logon fails [TOBIAS done 15/4]
- integrate Form- and Treehandling in AdCo [TOBIAS done 15/4]
- build ShiftBox AMS-Group selection (with two windows add/remove like in XBU) [TOBIAS done 16/4]
- change AMS-Groupprocessing on serverside (tokens to entities)[TOBIAS changed 17/4]
- confirmation on logout (generic confirmation-flag in Conmmand) [TOBIAS done 17/4]
- avoid server-startup on connection-failure (RMI-Registry) [TOBIAS done 17/4]
- errormessage if client cant connect to server prior to login [TOBIAS done 17/4]
- change AMS-Forms so ARPs will be set on save() not directly with a seperate Command [TOBIAS done 17/4]
- fix AMS-search [TOBIAS done 19/4]
- Copy+Paste in editor [TOBIAS done 19/4]
- introduce UserConfiguration for Modules [TOBIAS done 23/4]
- avoid focus-setting on read-only forms [TOBIAS done 23/4]
- Message on problems during session-initalisation [TOBIAS done 23/4]

GGI stands for General Graphics Interface, and it is a project that aims to develop a reliable, stable and fast graphics system that works everywhere. We want to allow any program using GGI to run on any platform, requiring at most a recompile.
Historically, GGI was developed in order to provide a unified interface to manage access to graphics hardware under Linux, to avoid the conflicts and instability arising from the direct access of hardware by competing graphics systems such as X and svgalib.
GGI project is now focussed on developing a set of portable user-space libraries, with an array of different backends or targets (eg. framebuffer, X, quartz, directx).
While GGI no longer aims to manage direct access to graphics hardware, we provide a target to use the interfaces provided by our associated KGI Project[->], which is concerned with providing the necessary kernel level support (protection, virtualization and abstraction) through a fast, secure and portable Kernel Graphics Interface.
Developed in a professional manner, the clean design, stability and scalability of GGI make it excellent in embedded, production and research environments, and it is user-supported with complete source.
The GGI project provides various libraries, of which the two most fundamental are LibGII (for input-handling) and LibGGI (for graphical output). All other packages add features to these core libraries, and so depend on one or both of them; for a more in-depth explanation of package categories, see the longer introduction to GGI.
Enhancements:
- Bootstrapping (aka running autogen.sh) now works with automake 1.10.
- display-lcd823, display-vgl, display-tile, display-quartz, crossblit, and generic blitting operations have been fixed.

The NIST Implementation of the Ad-Hoc On Demand Distance Vector protocol is a kernel-level driver for Linux . AODV is a routing protocol for ad hoc networks designed with mobile wireless devices in mind. For a quick overview on AODVs basics, check out our Quick Guide to AODV page. If you are interested in running a simulation of AODV, NIST has developed a simulation in OPNET.
Kernel AODV is a loadable kernel module for Linux. It implements AODV routing between computers equipped with WLAN interfaces.
This software was developed at the National Institute of Standards and Technology by employees of the Federal Government in the course of their official duties. Pursuant to title 17 Section 105 of the United States Code this software is not subject to copyright protection and is in the public domain. Kernel AODV is an experimental system. NIST assumes no responsibility whatsoever for its use by other parties, and makes no guarantees, expressed or implied, about its quality, reliability, or any other characteristic. We would appreciate acknowledgement if the software is used.
This software can be redistributed and/or modified freely provided that any derivative works bear some notice that they are derived from it, and any modified versions bear some notice that they have been modified.
Enhancements:
- Corrected LINK_LIMIT #ifdefs (Fix from Peter Barron)
- aodv_neigh.c
- hello.c
- module.c
- Add Packet Queuing back in (Fix from Peter Barron)
- Send queued messages when recieving a route, aodv_route.c
- Drop packet from queue if RREQ fails, rreq.c
- Added packet_queue.c back in, packet_queue.c
- Added init and cleanup of packet_queue, module.c
- Added additional check to packet_out.c to determine if packet is going to external subnet on a gateway.
- Shouldnt be neccesary since a route should be created for the external destination anyhow. Have to look into this. (Fix from Peter Barron)
- Removed annoying message printed when signal strength can not be read. Instead only prints when can not be set. signal.c
- Fixed the undefined symbol STRCHR problem for real this time. The problem is doing strstr() with a singlecharecter results in it being converted to strchr(), but for some reason it is not properly imported. The solution it to simply use stchr() instead. module.c
- Changed it so that find_aodv_route() will return valid routes that have expired. When it didnt return expired routes two routes would sometimes be created. Also, now kernel routes are only removed when an expired route is removed. find_aodv_route() will also invalidate expired valid routes.
- Had some trouble with duplicate kernel routes. Now we are always deleting before inserting a new route. Should fix it, fingers are crossed.
- Changed delete_neighbor() so that we send out an RERR even if the route is no longer valid. Also change gen_rerr() so that is will send out a RERR even if the route is not valid. It has to be better to send out a few extra rather than not enough. Just cause you have timed a route out doesnt mean others have.
- Compared the Metrics wrong in update_route() if the seq numbers were equal.

Esprit project is a Web-based learning management system, with an emphasis on collaborative work and strong pedagogical scenario.

pingmon is a small PING monitor, it just pings a server 5 times and displays the results.

Dont really know how usefull it will be to anyone, but here it is!

Change the .theme file to change the labels and the servers... ill try to do some sort of "click to change" thing later.

Wmufo is a dockable application which monitors your seti@home client statistics.

Installation:

Root Installation:

1) su -
2) cd /current/directory/of/wmufo
3) ./configure

Either

4A) make install-strip

or

4B) make
4B) strip src/wmseti
4B) cp src/wmseti /usr/local/bin/

User installation

1) ./configure
2) make
3) strip src/wmseti
4) cp src/wmseti ~/bin

The benchmark program takes less than 10 minutes to run (on most machines) and compares the system it is run on to two benchmark systems (a Dell Pentium 90 with 256 KB cache running MSDOS and an AMD K6/233 with 512 KB cache running Linux).

The archive contains the complete source, documentation, and a binary (Linux elf). The source has been successfully compiled on various operating systems, including SunOS, DEC Unix 4.0, DEC OSF1, HP-UX, DEC Ultrix, MS-DOS, and of course Linux.

This release is based on the Unix port of beta release 2 of BYTE Magazines BYTEmark benchmark program (previously known as BYTEs Native Mode Benchmarks). The port to Linux/Unix was done by Uwe F. Mayer.

Additional changes to the code were made to make the code work with egcs compiler and to make the software packagable. This is a CPU benchmark providing indexes for integer, floating, and memory performance. It is single-threaded and is not designed to measure the performance gain on multi-processor machines.

Running a "make" will create the binary if all goes well. It is called "nbench" and performs a suite of 10 tests and compares the results to a Dell Pentium 90 with 16 MB RAM and 256 KB L2 cache running MSDOS and compiling with the Watcom 10.0 C/C++ compiler.

If you define -DLINUX during compilation (the default) then you also get a comparison to an AMD K6/233 with 32 MB RAM and 512 KB L2-cache running Linux 2.0.32 and using a binary which was compiled with GNU gcc version 2.7.2.3 and GNU libc-5.4.38.

The algorithms were not changed from the source which was obtained from the BYTE web site at http://www.byte.com/bmark/bmark.htm on December 14, 1996. However, the source was modified to better work with 64-bit machines (in particular the random number generator was modified to always work with 32 bit, no matter what kind of hardware you run it on).

Furthermore, for some of the algorithms additional resettings of the data was added to increase the consistency across different hardware. Some extra debugging code was added, which has no impact on normal runs.

In case there is uneven system load due to other processes while this benchmark suite executes, it might take longer to run than on an unloaded system.

This is because the benchmark does some statistical analysis to make sure that the reported results are statistically significant, and an increased variation in individual runs requires more runs to achieve the required statistical confidence.

This is a single-threaded benchmark and is not designed to measure the performance gain on multi-processor machines.

Rekall is a database front-end, somewhat in the style of MicroSoft Access. However, Rekall is not itself a database, and does not include a database.
By this we mean that data is stored somewhere else in an SQL server, and Rekall is fundementaly just a tool to extract, display and update that data (of course, it does lots more than that, it does forms and reports and scripting and .... you get the idea).
It is database agnostic, and does not have any preferred database in the sense that Access(tm) uses the Jet. database engine (although the Windows version can use the Jet database engine via an ODBC driver).
Rekall can do lots of the things that you would expect of a database front-end (or if it cant, let us know!). You can design and use forms and reports, you can construct database queries, and you can import and export data (actually, you can copy data, import is just copy file to table, and export is just copy table to file). You can also create reusable components which you can use in forms and reports, to reduce application development time.
Rekall can be scripted using the the Python language. You can arrange that a script is executed when various events occur (for instance, when the user changes the value of a control).
Scripts can be associated directly with the event, but you can also store scripts in script modules for more general use. And, of course, you have full access to all the modules that are available for Python. Plus, Rekall has an integrated Python debugger with syntax highlighting.
RekallRevealed is run as a community website to support the GPL version of Rekall. Rekall is being included by some of the Linux distributions, and commercial components and support are available from TotalRekall and from theKompany.
Enhancements:
Dynamic Layouts
- Dynamic layouts allow you to create forms where controls automatically resize depending on settings such as font sizes, and as the user resizes the form. This is based on QTs layout engine, althougn only a restricted set of functions are available.
Tool Boxes
- Personally, the author is not a fan of tool boxes, but they seem to be popular, so Rekall now supports them. If you still prefer the old context menu mechanism, you can turn tool boxes off.
Wizards
- Lots of the controls now have control wizards which prompt you for the important settings. Hopefully wizards will be avaialble for all controls by the time 2.3.x becomes 2.4.0
Stock Databases
- Stock databases. Rekall will come with some stock databases (actually there is only one at present, the demo database, but more will be added over time) which can be used to create your own database. In addition, you can download stock databases from the web. See the Rekall section on downloading the database that runs this website!
Manual
- The manual can now be accessed via a dedicated manual viewer (loosely modelled on QTs assistant program).
Other stuff
- Lots of bug fixes, lots of other smaller additions.
Enhancements:
- 2.2.6 is the now latest stable release.
- Mostly bug fixes since 2.2.4, particularly a problem related (I believe) to the default style used by Fedora Core 4