Free otrs 2.2.2 software for linux

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.

GnoTime provides a to-do list organizer and project timer.
GnoTime is a to-do list tracker and project timer with a built-in invoice generator. It allows users to keep track of how much time they have spent working on particular tasks, maintain a diary of that work, and create invoices with task-specific billing fees and rates.
Main features:
- Multiple To-Do Lists that can be sorted by the priority/importance of the tasks in the list. The to-do items can be organized into categories, arranged in a hierarchical way. This makes it easy to maintain both business and personal items in the list, or handle many different projects, while keeping them separate from each other.
- A pair of Diary/Journal areas that can be used to keep long and detailed notes and diary entries. The project description area allows a multi-paragraph description or status to be typed in. The diary area allows day-to-day notes to be associated with a set of timestamps, so that one has a record of what one did on any given day.
- A Running Timer, with time totals, for each project/task. One starts the timer by clicking on a task: it will measure the amount of time that you are in front of the computer. If it detects that the keyboard/mouse are idle, it will stop the clock. If the clock stays stopped too long, it will nag you to start it up again. You can view time totals by day, week, month or year.
- A Billing Status dialog for each diary entry. You can mark any given diary entry as bill-able/non-bill-able, paid or pending, and set the billing rate. Each project can also be marked up with a set of project-planning information: planed start, end and due dates, hours to finish, percent-complete. This is in addition to assigning an urgency/importance to each project, as well as a status (completed/in-progress not-started/canceled).
- A half-dozen different HTML Reports that can slice and dice your lists. Theres a Journal report that shows all of the diary entries for one given project. Theres an Invoice report that summarizes the time spent on each entry, and computes a dollar amount for it. Theres a Status Report that prints the title of each project, together with the paragraph-long descriptions of each. Theres a ToDo report, which prints only the project title, the importance/urgency, and the completed/in-progress/not-started status. The Daily report summarizes the total time spent on a day-by-day basis, and lists each of the projects that were worked on in a given day. Each of these reports can be customized. And, because theyre HTML, you can even publish them as web pages. (Yes, Ive thought of using GnoTime as a weblog management/publishing tool).
Enhancements:
- Build against QOF version 0.6.0, if available.
- Fix issue where yelp doesnt display an entry for gnotime when browsing because it doesnt recognize the entry
- Fix sourceforge bug [ 799077 ] projects blanked when first time user tries to sort
- fix broken leap-year calculation, leading to bugs sourceforge bugs [ 983408 ] and [ 1114205 ]
- Fix crash due to hoverhelp timer popping after a report window is closed.
- Change activity report to display date/time in two distinct html table columns (prettier alignment)
- Bug fix: sourceforge bug report fixed [ 877193 ] toolbar wont go to/stay in text-only mode
- Bug fix: editing time brings up wrong report
- fedora .spec file is out of date and rpm cannot build rpm
- Fix bug involving copy of old gnotime files to a new machine on which gnotime has never been run before.
- Fix sourceforge bug [ 1276458 ] "Empty" appears in diary entry
- Apply sourceforge patch 1176719 Extensible fix for gtkhtml3 building
- Apply 1171394 Adds separate timeout for "No Project" dialog
- Apply sourceforge patch 085911 Add "-" value for status field
- Apply sourceforge patch 074658 Add wordwrapping to diary entry boxes
- Apply sourceforge patch 1074458 Fix a crash when invoking help
- Apply sourceforge patch 1038701 Fix to Activity item in popup menu
- Apply sourceforge patch 1027582 Build system update for qof inclusion
- Fix idle time so that it works with Linux 2.6 kernel /proc/interrupts
- use %e to see the estimated sizing of a project in the logfiles
- Apply new pt_BR translation from Goedson Teixeira Paixao
- Fix for Debian Bug #250776, change widget visibility in the edit interval dialog

jGGTrans is a gateway between Jabber/XMPP and Gadu-Gadu (which is a very popular proprietary instant messaging protocol in Poland).

GG Transport allows Jabber users to use their favorite XMPP client to talk with their GG-using friends.

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.

ziproxy is forwarding, non-caching, compressing proxy server. ziproxy squeezes images by converting them to low quality jpegs and optionally can also gzip HTML and other text-like data. ziproxy is intended to free bandwidth on dialup connections.

Can be run using inetd, xinetd, or you can use simple replacement "netd" that is part of this package. Former name of this project was mwp_proxy.

Installation:

To see your options, run:

./configure --help

Then run:

./configure

make

make install

Gallery is a web based software product that lets you manage your photos on your own website. You must have your own website with PHP support in order to install and use it.
With Gallery you can easily create and maintain albums of photos via an intuitive interface. The function photo management includes automatic thumbnail creation, image resizing, rotation, ordering, captioning, searching and more.
Albums can have read, write and caption permissions per individual authenticated user for an additional level of privacy. Give accounts to your friends and family and let them upload and manage their own photos on your website!
Main features:
- Image Magick or NetPBM - pick which image manipulation package you have on your server or want to use.
- Auto Rotate Images - Gallery can look at information in pictures from digital cameras and automatically rotate them as needed.
- Image Quality and Size Defaults - You can limit the quality and size of images so that when images are uploaded, Gallery will resize them to save space.
- Main Gallery Page Settings - The configuration wizard contains all of the settings for how the main Gallery page looks and acts including showing or hiding the album tree, search engine, or album owner, and what frames to show around albums.
- Optional Binaries: zip, jhead, jpegtran - If you have these programs on your webserver, you can enable them to make gallery work better and be more flexible.
- Languages - Choose which languages you want your Gallery to support and how the user is presented with the choice.
- Email Support - Set up email support to have your Gallery email users when their accounts are created or when they forget their password, email you copies, email people when the Gallery is updated, and more!
- Gallery-wide Slideshow - enable or disable a slideshow that includes all pictures in the gallery
- Commenting - turn off or on the public commenting system and configure it.
- Logging - enable logging with syslog or the Windows logger
- RSS publishing - publish your Gallery with RSS![1]
- Album Defaults - set defaults for the way that all new albums will originally look.

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.