Free sr software for linux

The SR-RTP library enables real-time streaming applications (such as streaming MPEG-4 video) to cope with packet loss, variable bandwidth, and variable delay on the Internet.

It provides a means for selective retransmission of lost packets in a fashion that is backwards-compatible with RTP. Additionally, it provides integration with the Congestion Manager to provide a system capable of performing TCP- friendly streaming of real-time data.

Installation:

The `configure shell script attempts to guess correct values for various system-dependent variables used during compilation.

It uses those values to create a `Makefile in each directory of the package. It may also create one or more `.h files containing system-dependent definitions.

Finally, it creates a shell script `config.status that you can run in the future to recreate the current configuration, a file `config.cache that saves the results of its tests to speed up reconfiguring, and a file `config.log containing compiler output (useful mainly for debugging `configure).

If you need to do unusual things to compile the package, please try to figure out how `configure could check whether to do them, and mail diffs or instructions to the address given in the `README so they can be considered for the next release.

If at some point `config.cache contains results you dont want to keep, you may remove or edit it.

The file `configure.in is used to create `configure by a program called `autoconf. You only need `configure.in if you want to change it or regenerate `configure using a newer version of `autoconf.

The simplest way to compile this package is:

1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system. If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute
`configure itself.

Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.

2. Type `make to compile the package.

3. Optionally, type `make check to run any self-tests that come with the package.

4. Type `make install to install the programs and any data files and documentation.

5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean.

There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.

STUX is a bootable CD with a collection of GNU/Linux software, automatic hardware detection, and support for many graphics cards, sound cards, SCSI and USB devices and other peripherals.
Stux OS target is to build a Live CD similar to KNOPPIX but based on Slackware Linux.
Main features:
- Window Managers: KDE 3.1, Gnome 2.4, fvwm2, fvwm95, WindowMaker, Twm
- Browsers: Mozilla 1.6, Konqueror, Galeon, Nautilus, Lynx, KGet, wget, ...
- Mail clients: Mozilla Mail, KMail, mail, ...
- News readers: Mozilla News, Knode, Pan, ...
- Office, Word Processing, Editors: Open Office 1.1.0, KOffice, AbiWord, Kedit, KWrite, Kate, Xpdf, ...
- Services: Apache 1.3.28, ProFTPd 1.2.8p, Ample, Samba, Secure Shell, MySqld
- Multimedia: VideoLan Client 0.5.2, XawTV, gqRadio, Xine,...
- Graphics: the Gimp, KPaint, XPaint,...
- Developing: gcc 3.2.3, g++, J2sdk 1.4.2, perl 5.8.0, python 2.3.1, php 4.3.3, ...
- IRC Client: Kopete, KSirc, Chatzilla!
- AIM Client: Kopete, Kit
- ICQ Client: Kopete
- Peer 2 Peer/File sharing: BitTorrent, xMule
- Data Base: mysql 4.0.15a
- Web Applications: phpMyAdmin 2.5.5
- KDE Languages: AF, AR, BG, BS, CA, CS, DA, DE, EL, EN, EN_GB, EO, ES, ET, EU, FA, FI, FR, HE, HR, HU, IS, IT, JA, LT, MK, MT, NB, NL, NN, NSO, PL, PT, PT_BR, RO, RU, SE, SK, SL, SR, SS, SV, TA, TH, TR, UK, VEN, VI, XH, ZH_CN, ZH_TW, ZU
Enhancements:
- Upgraded to Slackware current as at 1 Jun 2007 and KNOPPIX live CD 5.1.1 (kernel 2.6.19); fixed problem with installation on SATA hard disks; all STUX utilities deeply reviewed; NVIDIA proprietary driver updated to 1.0-9755 + legacy driver 1.0-9631 for old cards; save live CD persistent configuration on ReiserFS partitions; install compressed image on ReiserFS partitions; Acx wireless firmware upgraded; fully integrates with other pre-installed operating systems; Compiz 0.5.0; fully VMware/QEMU compatible.

Dark Lands project is an ANSI based RPG game.
Dark Lands is a multiplayer RPG made fully with ANSI graphics. The source code is in Pascal. Currently, this game has probably no point except exploring the areas and killing monsters. It can be used as a BBS door game.
Main features:
- Door.sys, doorfile.sr and chain.txt support
- up to 115200 bps speed and up to 99 comports
- Easy setup and installation
- Local mode play
- 12 major races and over 60 subraces, including Humans, Dragons, Elf, Undead and Lycanthropes.
- 9 character alignement combinaison are possible
- 12 god to chose from, and player can be atheist
- over 100 different rooms
- over 15 monsters
- over 200 racial skills and 13 racial disadvantaged (most are still not implemented)
- Require a Fossil driver to work
- Online help system
- Players can build their own cities, raise armies and manage it
- And, best of all, this is emailware, just complete the form in the email section and youll receive your registration key at no charge at all.
Enhancements:
- BBS independant operation (optionnal)
- Internal login system
- Max time on
- Daemon operation DPMI + Linux are now functionnal ports.
- Faster Disk i/o
- Sysop can disable the sysop keys in the setup. (security)

GNU ccRTP is an implementation of RTP, the real-time transport protocol from the IETF (see RFC 3550, RFC 3551 and RFC 3555). ccRTP is a C++ library based on GNU Common C++ which provides a high performance, flexible and extensible standards-compliant RTP stack with full RTCP support. The design and implementation of ccRTP make it suitable for high capacity servers and gateways as well as personal client applications.
In designing ccRTP, we have taken into account that RTP has been defined as an application level protocol framework rather than a typical Internet transport protocol such as TCP and UDP. Thus, RTP is hardly ever implemented as a layer separated from the application.
Consequently, RTP applications often must customize the adaptable RTP packet layout and processing rules, timing constraints, session membership rules as well as other RTP and RTCP mechanisms. ccRTP aims to provide a framework for the RTP framework, rather than being just an RTP packet manipulation library.
Support for both audio and video data is also considered in the design of ccRTP, that can do partial frame splits/re-assembly. Unicast, multi-unicast and multicast transport models are supported, as well as multiple active synchronization sources, multiple RTP sessions (SSRC spaces), and multiple RTP applications (CNAME spaces). This allows its use for building all forms of Internet standards based audio and visual conferencing systems.
GNU ccRTP is threadsafe and high performance. It uses packet queue lists for the reception and transmission of data packets. Both inter-media and intra-media synchronization is automatically handled within the incoming and outgoing packet queues. GNU ccRTP offers support for RTCP and many other standard and extended features that are needed for both compatible and advanced streaming applications.
It can mix multiple payload types in stream, and hence can be used to impliment RFC 2833 compliant signaling applications as well as other specialized things. GNU ccRTP also offers direct RTP and RTCP packet filtering.
GNU ccRTP uses templates to isolate threading and sockets related dependencies, so that it can be used to impliment realtime streaming with different threading models and underlying transport protocols, not just with IPV4 UDP sockets. For a more detailed list of ccRTP features you can have a look at the programmers manual.
At its highest level, ccRTP provides classes for the real-time transport of data through RTP sessions, as well as the control functions of RTCP.
The main concept in the ccRTP implementation of RTP sessions is the use of packet queues to handle transmission and reception of RTP data packets/application data units. In ccRTP, a data block is transmitted by putting it into the transmission (outgoing packets) queue, and received by getting it from the reception (incoming packets) queue.
Main features:
- Highly extensible to specialized stacks.
- Supports unicast, multi-unicast and multicast. Handles multiple sources (including synchronization sources and contributing sources) and destinations. Also supports symmetric RTP.
- Automatic RTCP functions handling, such as association of synchronization sources from the same participant or NTP-RTP timestamp mapping.
- Genericity as for underlying network and transport protocols through templates.
- It is threadsafe and supports almost any threading model.
- Generic and extensible RTP and RTCP header validity checks.
- Handles source states and information as well as statistics recording.
- Automatically handles SSRC collisions and performs loop detection.
- Implements timer reconsideration and reverse reconsideration.
- Provides good random numbers, based on /dev/urandom or, alternatively, on MD5.
There are several levels of interface (public interface, public or protected inheritance, etc) in ccRTP. For instance, the rtphello demo program distributed with ccRTP just uses the public interface of the RTPSession class and does not redefine the virtual method onGotSR, thus what this program knows about SR reports is the information conveyed in the last sender report from any source, which can be retrieved via the getMRSenderInfo method of the SyncSource class.
On the contrary, the rtplisten demo program redefines onGotSR by means of inheritance and could do specialized processing of these RTCP packets. Generally, both data and control packets are not directly accessible through the most external interface.
All this functions are performed through a few essential classes and types. The most basic ones are the enumerated type StaticPayloadType, and the classes StaticPayloadFormat and DynamicPayloadFormat.
The most important ones are the classes RTPSession, SyncSource, Participant and AppDataUnit, that represent RTP sessions, synchronization sources, participants in an RTP application, and application data units conveyed in RTP data packets, respectively.
When using ccRTP, both sending and receiving of data transported over RTP sessions is done through reception and transmission queues handled by the RTP stack. In the most common case, a separate execution thread for each RTP session handles the queues. This case is the threading model that we will generally assume throughout this document. Note however that ccRTP supports other threading models, particularly ccRTP supports the use of a single execution thread to serve a set of RTP sessions. It is also possible to not associate any separate thread with any RTP session, manually calling the main data and control service methods from whatever other thread.
The basic idea for packet reception with ccRTP is that the application does not directly read packets from sockets but gets them from a reception queue. The stack is responsible for inserting received packets in the reception queue and handling this queue. In general, a packet reception and insertion in the reception queue does not occur at the same time the application gets it from the queue.
Conversely, the basic idea for packet transmission with ccRTP is that packets are not directly written to sockets but inserted in a transmission queue handled by the stack. In general, packet insertion and transmission occur at different times, though it is not necessary.
In order to use ccRTP, you must include the main header (#include < ccrtp/rtp.h >. Two additional headers are provided by ccRTP:
#include < ccrtp/rtppool.h
Classes for pools of RTP service threads.
#include < ccrtp/rtpext.h >
Classes for RTP extensions which are not mature yet.
You must also link in the library, currently ccrtp1.
Enhancements:
- Brand new support has been introduced for Secure RTP Profile (srtp) as per RFC 3711.
- This release also supports a new add-on package, libzrtpcpp, that directly offers native zfone (zrtp) compatible encryption capabilities to Common C++ RTP based applications.
- This is the first softphone client to use both Common C++ RTP srtp and zrtp support.

ac3info project is a tool that extracts some basic information from an AC3 file.

Example:

ac3info bjorn.ac3

AC3 Informations for bjorn.ac3
Basic Informations
- Channels : 5.1
- Sample Rate : 48000 Khz
- Bitrate : 448 Kbits/sec

Advanced Informations
- Bit Stream Mode : main audio service: complete main (CM)
- Channels Ordering : L,C,R,SL,SR
- Cmix level : -3.0 dB
- Surround Mix level : -3.0 dB

gFTP is a free multithreaded file transfer client for *NIX based machines running X11R6 or later. gFTP has text and GTK+ 1.2/2.x interfaces and supports the FTP, FTPS (control connection only), HTTP, HTTPS, and SSH protocols and has FTP and HTTP proxy server support. It supports UNIX, EPLF, Novell, MacOS, VMS, MVS, and NT (DOS) style directory listings, and has a bookmarks menu that allows you to quickly connect to remote sites. The code is fully internationalized and there are currently 40 translations available.
Main features:
- Distributed under the terms of the GNU Public License Agreement
- Written in C and has a text interface and a GTK+ 1.2/2.x interface
- Supports the FTP, FTPS (control connection only), HTTP, HTTPS and SSH protocols
- FTP and HTTP proxy server support
- Supports FXP file transfers (transfering files between 2 remote servers via FTP)
- Supports UNIX, EPLF, Novell, MacOS, VMS, MVS and NT (DOS) style directory listings
- Bookmarks menu to allow you to quickly connect to remote sites
- Fully Internationalized. Here are the followoing translations of gFTP that are available: Albanian (sq), Amharic (am), Arabic (ar), Azerbaijani (az), Bangla (bn), Belarusian (be), Bulgarian (bg), Catalan (ca), Chinese (zh_TW,zh_CN), Croatian (hr), Czech (cs), Danish (da), Dutch (nl), English (en_CA, en_GB, en_US), Finnish (fi), French (fr), German (de), Greek (el), Hebrew (he), Hungarian (hu), Irish (ga), Italian (it), Korean (ko), Japanese (ja), Macedonian (mk), Malayalam (ml), Malay (ms), Norwegian (no), Polish (pl), Portuguese (pt,pt_BR), Punjabi (pa), Romanian (ro), Russian (ru), Serbian (sr,sr@Latn), Slovak (sk), Spanish (es), Swedish (sv), Tamil (ta), Thai (th), Turkish (tr) and Ukrainian (uk) translations available.

FoxGame is an extension that can be used to enhance user experience with O-game.
Enhance user experience with O-game (now works in every o-game version)
Adds a lot of features to the webgame O-game.
It also integrates Database features inside the game.
O-Game, is a real-time spacial browser game.
bs-BA/hr-HR/cs-SR can be downloaded as a separate version from http://foxgame.mozdev.org/ because there is no especific firefox version for those languages.
Main features:
- Automatic universe selector in login page.
- Reduced galaxy view: Planet column is not rendered and its functinality is moved to Name col., debris header reduced also.
- Extra delete options and spy report options: You can control messages from the top or the bottom.
- Fleet arrival and return time: In fleet destiny selection page you will see the time when you fleet will arrive and come back to your planet.
- Fleet retreat time: In fleet page you will see the time when your fleet will arrive if you order to come back.
- Multilanguage support: es-ES(spanish), en-US(english), de-DE(deutsch), pl-PL(polish), fr-FR(french), nl-NL/nl-BR (dutch), it-IT (italian), bs-BA/sr-CS/hr-HR (bosnian, serbian, croatian), pt-PT/pt-BR(portugese), tr-TR(Turkish), zh-CN/zh-TW (Simplified chinese and traditional chinese), ru-RU (russian), da-DK (danish), si-SL (slovenian) and sv-SE/sv-FI (swedish). If your language is not supported and you want to translate it, mail me.
- Almost all finishing hours: Research and buildings finishing hours, hangars qeue finishing time, you can see date/time in overview if you wish and even in phalanx.
- Highlight ally and private messages: Ally and private messages now have a diferent background to see them easily.
- Highlight big debris fields: Debris fields bigger than you fix min will have different background in galaxy view.
- Autochoose mision type: You can define mission priorities so FoxGame will select the mission according to that.
- Online DBs integration: Send reports to Milos (only ogame.com.es), EspRep and GalaxieTool directly within OGame (solar systems, stats and spy reports supported).
- In mines and power plants info screens (the ones you see when you click in the name) you will see the diferences between your actual level and the rest.
- Autoselect fleet destination: Select coord text anywhere go to fleet send screen and Voila! the destination is already selected. There is no need to take down numbers anymore.
- Private message signatures.

giFToxic provides a GTK 2-based client for giFT.
At the moment it is under heavy development.
giFT stands for giFT: Internet File Transfer. It is a daemon that is intended to act as a bridge to combine the capability of using several (peer-to-peer or otherwise) file sharing protocols for a simple GUI client.
It uses the plugin paradigm to dynamically load different protocols for a client as and when required. The currently supported networks include:
Stable
OpenFT, giFTs own file sharing network
Gnutella1 (used by BearShare, LimeWire, ...)
Ares Galaxy
Turtle F2F
Beta
FastTrack (used by Kazaa)
Alpha
OpenNap
eDonkey
Soulseek
A lightweight protocol is used by clients to communicate with the giFT process, allowing the protocol code to be completely abstracted from the user interface.
Search nodes handle search requests. They search the filelists their CHILD (common) nodes submitted to them. These nodes must have a capable Internet connection and at least 128M RAM. A modern processor is highly recommended as well.
INDEX nodes keep lists of available search nodes, collect statistics, and try to maintain the structure of the network.
Enhancements:
- fixed escaping
- dont start a source search when a transfer is started
- recycle upload slots
- fixed daemon autostart mode
- Languages added: hr, ms, fr, cs, az, sk, pt, sr, sv