Free 1.1.4 firmware software for linux

Tomato Firmware is a small, lean, simple replacement firmware for Linksys WRT54G/GL/GS and Buffalo WHR-G54S/WHR-HP-G54 routers.

It features a new easy to use GUI, a new bandwidth usage monitor, more advanced QOS and access restrictions, enables new wireless features such as WDS and wireless client modes.

It raises the limits on maximum connections for P2P, allows you to run your custom scripts or telnet/ssh in and do all sorts of things like re-program the SES/AOSS button, adds wireless site survey to see your wifi neighbors, and more.

firmware-tools is an architecture that utilizes native Linux packaging formats (.rpm and .deb) and native Linux change management frameworks (yum, apt, etc) for delivering and installing system firmware. firmware-tools architecture is OS distribution, hardware vendor, device, and change management system agnostic.
The architecture is easy as PIE: splitting Payload, Inventory, and Executable components into separate packages, using package format Requires/Provides language to handle dependencies at a package installation level, and using matching Requires/Provides language to handle runtime dependency resolution and installation ordering.
The framework then provides unifying applications such as inventory_firmware and apply_updates that handle runtime ordering of inventory, execution, and conflict resolution/ notification for all of the plug-ins. These are the commands a system administrator runs. Once all of the separate payload, inventory, and execution packages are in package manager format, and are put into package manager repositories, then standard tools can retreive, install, and execute them:
# yum install $(inventory_firmware -b)
# apply_updates
Enhancements:
- Initial stable proposed API and initial CLI.
- Several small typos for names of commands have been fixed.
- Tested with the first public release of firmware-addon-dell for updating select Dell system BIOSs across Dell servers, desktops, and laptops.

FLAC is Free Lossless Audio Codec. Grossly oversimplified, FLAC is similar to MP3, but lossless, meaning that audio is compressed in FLAC without any loss in quality.
This is similar to how Zip works, except with FLAC you will get much better compression because it is designed specifically for audio, and you can play back compressed FLAC files in your favorite player (or your car or home stereo, see supported devices) just like you would an MP3 file.
FLAC is freely available and supported on most operating systems, including Windows, "unix" (Linux, *BSD, Solaris, OS X, IRIX), BeOS, OS/2, and Amiga. There are build systems for autotools, MSVC, Watcom C, and Project Builder.
The FLAC project consists of:
the stream format
reference encoders and decoders in library form
flac, a command-line program to encode and decode FLAC files
metaflac, a command-line metadata editor for FLAC files
input plugins for various music players
When we say that FLAC is "Free" it means more than just that it is available at no cost. It means that the specification of the format is fully open to the public to be used for any purpose (the FLAC project reserves the right to set the FLAC specification and certify compliance), and that neither the FLAC format nor any of the implemented encoding/decoding methods are covered by any known patent. It also means that all the source code is available under open-source licenses. It is the first truly open and free lossless audio format.
Main features:
- Lossless: The encoding of audio (PCM) data incurs no loss of information, and the decoded audio is bit-for-bit identical to what went into the encoder. Each frame contains a 16-bit CRC of the frame data for detecting transmission errors. The integrity of the audio data is further insured by storing an MD5 signature of the original unencoded audio data in the file header, which can be compared against later during decoding or testing.
- Fast: FLAC is asymmetric in favor of decode speed. Decoding requires only integer arithmetic, and is much less compute-intensive than for most perceptual codecs. Real-time decode performance is easily achievable on even modest hardware.
- Hardware support: Because of FLACs free reference implementation and low decoding complexity, FLAC is currently the only lossless codec that has any kind of hardware support.
- Streamable: Each FLAC frame contains enough data to decode that frame. FLAC does not even rely on previous or following frames. FLAC uses sync codes and CRCs (similar to MPEG and other formats), which, along with framing, allow decoders to pick up in the middle of a stream with a minimum of delay.
- Seekable: FLAC supports fast sample-accurate seeking. Not only is this useful for playback, it makes FLAC files suitable for use in editing applications.
- Flexible metadata: New metadata blocks can be defined and implemented in future versions of FLAC without breaking older streams or decoders. Currently there are metadata types for tags, cue sheets, and seek tables. Applications can write their own APPLICATION metadata once they register an ID
- Suitable for archiving: FLAC is an open format, and there is no generation loss if you need to convert your data to another format in the future. In addition to the frame CRCs and MD5 signature, flac has a verify option that decodes the encoded stream in parallel with the encoding process and compares the result to the original, aborting with an error if there is a mismatch.
- Convenient CD archiving: FLAC has a "cue sheet" metadata block for storing a CD table of contents and all track and index points. For instance, you can rip a CD to a single file, then import the CDs extracted cue sheet while encoding to yield a single file representation of the entire CD. If your original CD is damaged, the cue sheet can be exported later in order to burn an exact copy.
- Error resistant: Because of FLACs framing, stream errors limit the damage to the frame in which the error occurred, typically a small fraction of a second worth of data. Contrast this with some other lossless codecs, in which a single error destroys the remainder of the stream.
What FLAC is not:
- Lossy. FLAC is intended for lossless compression only, as there are many good lossy formats already, such as Vorbis, MPC, and MP3 (see LAME for an excellent open-source implementation).
- SDMI compliant, et cetera. There is no intention to support any methods of copy protection, which are, for all practical purposes, a complete waste of bits. (Another way to look at it is that since copy protection is futile, it really carries no information, so you might say FLAC already losslessly compresses all possible copy protection information down to zero bits!) Of course, we cant stop what some misguided person does with proprietary metadata blocks, but then again, non-proprietary decoders will skip them anyway.

STuNT is a ticketing system, custom made to cover the needs of Space Hellas. STuNT is a web based application, build with simplicity and ease of use in mind. STuNT was designed to facilitate the work of support technicians and customers technicians while avoiding to add another layer of bureaucracy.
Main features:
- Web based. Minimum javascript used. Works even in text (console) browsers.
- Informational e-mails for each important action.
- Reminder (escalation) e-mails depending on case severity.
- Flie transfer facilities for each case.
- Complete action history for each case.
- Complete reminder e-mail history.

Pulga is a program for numerical simulation of dynamical systems. Pulga project is designed to provide a way for students and researchers who study dynamical systems to model them on a computer and analyze them numerically without the difficulty of traditional computer programming languages.

As we grow up learning math at school we face the joy of dealing with loads of numbers and their pretty properties but as soon as we start to study the real thing in a university we face our first problem.

Although we love to write complex formulas most of us have not that much fun dealing with computer programming, which has proved to be useful and sometimes even essential for some researchs. And that does not only happens with students as there are some teachers and researchers who have exactly the same fear of facing some code.

The classes could be funier and more dynamic, the students would be able to analyse intricate dynamical systems and researchers would not have to worry to learn the newest trend on computer programming in order to get what they need: whether it is for researching, teaching, simulating or studying, there is a need for an open source tool that should be capable of taking the computer code out of their way.

Xebian is a linux distribution based on Debian Linux for XboX.

With superb flexibility and ease of use, it can run live off CD/DVD or it can be installed onto the Xbox hard drive in either the free space or the saved game area.

The OS includes support for all versions of the Xbox, including those with Xcalibur video chips.

it is based on Debian Testing (Sarge) with backports for newer software.

The "Open Device Monitoring and Tracking Protocol", otherwise known as OpenDMTP, is a protocol and framework that allows bi-directional data communications between servers and devices (clients) over the Internet and similar networks.
OpenDMTP is a highly configurable and extensible protocol for communicating with mobile devices.
OpenDMTP is particularly geared towards Location-based information (LBS) such as GPS, as well as temperature and other data collected in remote-monitoring devices. OpenDMTP is small, and is especially suited for micro-devices such as PDAs, mobile phones, and custom OEM devices.
We saw a need for a communications protocol that allowed high-latency, low-bandwidth (HL/LB) devices to transmit location data to monitoring-systems. Because these devices often have limited network connectivity, the protocol needed to be small and efficient. Example devices include mobile phones, PDAs, OEM micro-devices (alarm systems, temperature monitors, etc.), and more.
There are many mobile GPS tracking devices on the market today with their own closed proprietary protocols. Searching the web for open protocols revealed only a few available for transferring data (including GPS information) between devices. However these solutions are generally designed for non-mobile applications and/or lack some of the low-bandwidth, configurable, and extensible features that mobile applications require.
Main features:
- Small Footprint: Mobile devices typically have limited resources on which to run client code (ie. memory, processor speed). An open protocol designed with this in mind should be optimized to allow efficient implementation and should easily support devices such as PDAs, mobile phones, GPS monitoring devices, and other OEM micro-devices.
- Network Efficient: Mobile devices typically have limited network connectivity, and in some cases data communication can be quite expensive (e.g. satellite). Because of this the protocol needs to be efficient in its dialog between the client and server. The communication needs to be optimized such that the necessary information can be conveyed with a minimum number of bytes in the least amount of time.
- Bi-directional: Some devices can support two-way communication (ie. GPRS, or other socket based connections), while others may only support one-way communication (ie. some satellite communication systems). With this in mind, a protocol should be designed to support both duplex (two-way) and simplex (one-way) communication.
- Transport Media: Differrent mobile applications will have their own unique way of communicating data back to the server. Some may use GPRS, or socket based communication, others may use satellite communication, while still others may use other forms of wireless communication, such as BlueTooth. The design of the protocol should be able to encompass all such transport media types, regardless of the type of transport in use.
- Flexible Data Encoding: Most types of transport media allow for the transmission of binary encoded data. However, there may be some forms of media for which an ASCII encoded data packet is much better suited. A protocol designed with this in mind should be able to support both types of data encoding.
- Configurable Messages: Due to the broad range of data types used in mobile applications, the protocol should be flexible enough to define standard messages, yet still allow custom messages within the framework.
- Extensible: Not every mobile application is the same. Some require special handling and may have various types of inputs and outputs. A protocol designed for mobile applications should insure that the framework can be easily extended to incapsulate the specific needs of the device.
- Industry Compatibility: Having an open protocol insures better compatibility between different client devices and service providers.
- Reference Implementation: Having a reference implementation that showcases the major features of the protocol provides an easy starting point on which developers can add their own features and platform specific implementation without having to worry about how data gets from the client to the server.
OpenDMTP was specifically designed to suit all these needs, especially "Small Footprint" and "Network Efficiency". The typical data plan for GPRS communication, for instance, is usually 1Mb per month. OpenDMTP was designed to optimize packet encoding to allow the collection of GPS information packets once every 3 minutes, 24 hours a day, 30 days a month, and still stay under the 1Mb data plan limit.
While XML is very extensible, it fails the "Small Footprint" and "Network Efficiency" requirements. Thus, it was discounted as a viable protocol solution. Many mobile devices do not have the resources necessary to be able to provide full XML parsing functionality. And an XML packet may need to be several hundred bytes in length just to send a few bytes of actual data. This alone would make the solution cost prohibitive for high-cost transport media such as satellite.
OpenDMTP also includes a full-featured commercial quality reference implementation to jump-start development.
Enhancements:
- NEW: Now includes a build target for creating a Servlet WAR file for delivering CSV, or KML(XML), formatted records over the web. KML formatted records can be imported directly into Google Earth (which also automatically retrieve periodic updates to the data) so that as new records come in to the MySQL database, they will automatically be updated in Google Earth.
- NEW: MySQL datastore server now has better error checking.
- NEW: The build-in logging facility has been updated with some additional features and provides an easier path for eventually porting to Log4J.

CitrusDB is an open source customer database application that uses PHP and a database back-end (currently MySQL).
This software can keep track of customer information, CRM, services, products, billing, and customer service information. The program will run on any PHP enabled web server.
This software is now in beta. There is still alot of room for tweaking code and making things more streamlined, a whole lot of room. The code of CitrusDB might even be able to be used now for something other than to play around with, but since its beta I wont recommend using it in production yet. For long time users, please note that the initial login name has changed from "test" to "admin" now!
Main features:
- modular functions to allow new pieces to work along side base functions
- security and password access to database on a per user level
- track modifications to customer records made by the database user
- keep general info, mailing address, billing address, and billing info about each customer
- able to assign multiple (unlimited?) services or products to a customer record
- add custom fields for services/product information
- trouble tickets / individual and department notifications
- import / export feature to send billing data back and forth to card processing software
- import from online order data (or online order component)
- search by specified fields
- easy to add and modify services/products
- ability to invoke remote commands to talk to other servers for billing queries, user lookups, etc.
- bill credit card and invoice for monthly, setup fee, onetime charges, 6 month, yearly, etc. billing cycles
- ability for different billing types to be assigned to each product or service that one customer has