Free july software for linux

Apalogretrieve program retrieves data from an Apache logfile with a syntax, that is derived (a subset of) the SQL language.

The idea to make such an implementation came up at 17th of July 2007. I just started it then.

The basic idea of using an SQL-like dialect for logfile-analysis I had many years ago, but as there was no necessity, I didnt started a project like this.

The reason why I started to implement it now is, that the idea about SQL-querying of a logfile was now of interest to me, because I hated the way, how webalizer does it: you have graphical results very easy, but how to make detailed lookups to certain information? And: what about the delay until the (averaging) data can be seen in the graphs, and other problems, when changing a webalizer.conf-file?

So, this was the reason to start it.

As I not every day have the time to implement it, and only do it in a spare time window, it might need some time to make it ready, but reading Apaches common logfile-format as well as parsing simple SQL-like SELECT statements already works (19th of July 2007).

Usage Example:

SELECT host,date FROM "apache-commonlog.log" where size > 2000;
SELECT host,date,client,referrer FROM "apache-commonlog.log" where host = "foobar.host.net";

Mr. Persister is a simple, small, object relational mapping API capable of reading Java objects from, and writing Java objects to relational databases. It was first released july 2004.
Main features:
- Fast! (Faster than Hibernate)
- Read objects of any size in just 3-5 lines of code.
- Automatic and manual mapping of objects to database tables.
- No config files required.
- SQL as query language.
- Automatic connection and transaction management
- (via DAO commands).
- Automatic connection and transaction management
- (via connection and transaction scoping).
- Automatic SQL generation for most trivial tasks.
- Batch updates of multiple objects.
- Compound primary key support.
- Partial object reading and writing.
- Read Filters.
- Simplifies trivial JDBC tasks.
- Interleave custom JDBC with Mr. Persister operations.
- Fully Pluggable Design.
- Well Tested. 290 unit tests were executed against each supported database.
Enhancements:
- Mr. Persister now uses JDK 5.0.
- Some important bugs have been fixed, and the software now enables annotation-based class-to-database mappings both as an alternative and a supplement to automatic and programmatic mapping.

ZIG is a client-server game networking engine. The current main version is "2", and it was launched in July, 2007 with ZIG 2.0.0. This software is free and it is licensed under a BSD-like license.
From the standpoint of ZIG, the graphics renderer, the sound engine and the input handler are all extensions you must provide. You will be able to plug your Allegro, SDL, DirectX, OpenGL etc. stuff into ZIG with ease. ZIG is a cross-platform C/C++ library which depends only on HawkNL versions 1.7 beta 1 or later.
Enhancements:
- This release brings about two years of bugfixes and enhancements, plus documentation rewritten from scratch.
- It includes SCTP-like transport of multiple message streams through a single ZIG client-server connection.
- Each stream enforces a message ordering that is independent of other streams.
- The ZIG streams also allow you to control bandwidth use (if you want to) and to mix reliable and unreliable messages on the same stream.

Syllable was born in July 2002 as a fork of the AtheOS operating system. Several AtheOS developers, concerned about the long-term development of AtheOS, created Syllable to ensure that development would continue.
Syllables goal is to create a reliable and easy-to-use open source operating system for the home and small office user. We also want to encourage developers to create an operating system that is intuitive, easy to use, and powerful.
Main features:
- Booting usually takes less than ten seconds
- A full GUI is built into the OS
- Support for a wide range of common hardware devices, including video, network, and sound cards from manufacturers such as Intel, AMD, 3Com, nVidia, and Creative (see Azaka for a complete list)
- Internet access through an Ethernet network (though PPP and PPPoE are not yet supported)
- A graphical web browser (ABrowse) and e-mail client (Whisper), and hundreds of other native applications (see Kamidake for a complete list)
- A journalled file system, modelled on the BeOS file system
- An application launcher (like the Windows Start button)
- 99% POSIX compliance
- GUI-based preferences tools for networking, display preferences, user administration, etc.
- The entire source is available via the GPL
- An object-oriented programming API

Jikes RVM is a compiler that translates JavaTM source files as defined in The Java Language Specification into the bytecoded instruction set and binary format defined in The Java Virtual Machine Specification.

You may wonder why the world needs another Java compiler, considering that Sun provides javac free with its SDK. Jikes has five advantages that make it a valuable contribution to the Java community: [OSI Certified Logo]

* Open source. Jikes is OSI Certified Open Source Software. OSI Certified is a certification mark of the Open Source Initiative.
* Strictly Java compatible. Jikes strives to adhere to both The Java Language Specification and The Java Virtual Machine Specification as tightly as possible, and does not support subsets, supersets, or other variations of the language. The FAQ describes some of the side effects of this strict language conformance.
* High performance. Jikes is a high performance compiler, making it ideal for use with larger projects.
* Dependency analysis. Jikes performs a dependency analysis on your code that provides two very useful features: Incremental builds and makefile generation.
* Constructive Assistance. Jikes strives to help the programmer write better code in two key ways. Jikes has always strived to provide clear error and warning text to assist the programmer in understanding problems, and now with release 1.19 Jikes helps point out common programming mistakes as documented in Effective Java.

Abridged from a FAQ entry which was adapted from some material by Lou Grinzo for an article he wrote.

The fact that Jikes is a high-performance, highly compatible Java compiler that can be used on almost any computing platform makes it an interesting program and worth investigating for almost any Java programmer. But Jikes is also notable because it lies at the center of two events: the adoption of open source philosophy and practice by large corporations, and the continued growth of Java for Linux.

Its worth pointing out that Jikes is not, and is not intended to be, a complete development environment -- it is simply a command line compiler. It should not be considered a replacement for more complete tools, such as Source Navigator or IBMs VisualAge for Java which provide sophisticated graphical IDEs (Integrated Development Environments).

The Jikes compiler was released in binary form in April 1997 on the IBM alphaWorks site. Jikes for Linux was released on 15 July 1998. The response was overwhelming -- Jikes had more downloads in the three months after the announcement than in the fifteen months before the announcement.

Around the end of March 2002, IBM opened a fledgling community hosting location attached to their developerWorks site with Jikes as a founding member. Approximately 3 years later this server was decommissioned and the most active projects migrated into SourceForge.net hosting options. During those three years Jikes was the #1 most popular project every month, often by a large margin. We approached nearly 250,000 downloads while residing at dw/oss, and had been consistently tallying triple digit daily downloads.

Release of Jikes for Linux was soon followed by requests to open up the source. Many notes and comments from users suggested this would be a good idea. The source was released under a liberal license in December 1998 to make a very visible demonstration of IBMs commitment to open standards and to Java Technology, to make Jikes more reliable and accessible, to encourage more widespread use of Java Technology, to encourage standardization of Java Technology, and to gain some experience actually running an open source project. This marked the start of one of IBMs first efforts in the open source arena.

The original alphaWorks version of Jikes was written by Philippe Charles and Dave Shields of the IBM T. J. Watson Research Center. For awhile after the release of the source they continued to work on the compiler as contributors; however, shortly after the project migrated to developerWorks Open Source Server they were officially moved off onto other projects within IBM. Today there are no IBMers who work on Jikes as part of their job description. Jikes survives today soley based on the free time contributions of members of the open source community.

The source code is available under IBMs Public License, which has been approved by the OSI (Open Source Initiative) as a fully certified open source license. The project provides access to the complete CVS development tree, which includes not only Jikes, but also the source for the Jacks Test Suite and the Jikes Parser Generator used to build Jikes. Jikes is included in many Open Source Operating Systems. The Jacks Test Suite is a replacement for the Jikestst package.

ferrisfuse is a FUSE module for mounting libferris filesystems through the Linux kernel.
About libferris
In non technical terms libferris makes the file system and other hierarchical storage systems easier to use. For the geeks out there, libferris is a virtual file system (VFS) that runs in the user address space. The FAQ contains entries related to installation, configuration and the usage of libferris.
As of July 2005 libferris can mount many interesting things ranging from a filesystem from your local Linux kernel through to LDAP, Evolution, PostgreSQL, dbXML, and RDF. To get an impression of the current capabilities of libferris mounting see the plugins/context directory of the lastest release. New things to mount are always being added.
Other than mounting things as a filesystem, the other core concept of libferris is extraction of interesting metadata from your libferris filesystems. This means that simple things like width and height of an image file become first class metadata citizens along with a files size and modification time. The limits on what metadata is available extend far beyond image metadata to include XMP, EXIF, music ID tags, geospatial tags, rpm metadata, SELinux integration, partially ordered emblem categories and arbitrary personal RDF stores of metadata.
Though some consider the last point of purely academic interest the end result is that you can add metadata to *all* libferris objects even those you only have read access too, for example, you can attach emblems to this website just as you would a normal file. The metadata interface gives all metadata from file size to digital signature status information equal standing. As such you can sort a directory by any metadata just as easily as you would ls -Sh to sort by file size. Sorting on multiple metadata values is also supported in libferris, you can easily sort your files by mimetype, then image width, then modification time with all three pieces of metadata contributing to the final directory ordering.
Late in 2004 extensive support for both fulltext and metadata indexing was added to libferris. This means you can supply queries against the contents or metadata of any libferris accessable object and have the results returned as a virtual filesystem. With the above mentioned metadata available for searching, finding your files can be done in many different ways instead of being forced to generate fixed directory trees using part of a file collections semantics as directory names. The metadata and virtual filesystem play together here allowing you to geospatially tag both your digital pictures, trip plans, and relevent websites and recall these objects in a single virtual directory no matter what their path or URL may be.
There is also a Samba VFS module which allows you to expose a libferris filesystem as a Samba share. Kfsmd uses the inotify kernel interface to allow libferris to watch changes made to your kernel filesystem by non libferris applications and update its indexes appropriately. Ferriscreate provides a command line and GTK+2 application for creating "new files" with libferris. With this you can create a new db4 database, dbXML database or fulltext index just as easily as you can make a regular file.
The ego filemanager is a GTK+2 interface built on top of libferris. It provides GTK treeview , gevas/edje and gecko based interfaces and makes extensive use of libferris clients to provide its functionality.
If you have a project you wish to use libferris with and want extensions made dont hesitate to contact one of the developers to arrange consulting.
For the geeks out there, libferris is a virtual file system (VFS) that runs in the user address space. At the moment libferris is a shared object that each application can dynamically link to in order to see the file system through a nicer abstraction.
New additions to the XML module allow for data to be converted from one format to another by the VFS for you. To copy data to an XML file:
fcreate --create-type=xml --rdn=2.xml root-element=fred /tmp
gfcp -av Makefile.am --dst-is-dir /tmp/2.xml/fred
To copy data to a db4 file
fcreate --create-type=db4 --rdn=2.db /tmp
gfcp -av Makefile.am --dst-is-dir /tmp/2.db
Ferris presents a C++ interface that makes heavy use of the STL and IOStreams. Currently ferris has two main internal abstractions: Context and Attribute. A context is much like a traditional file or directory in a file system, the major differences being that a context can have both byte content (like a file) and subcontexts (like a directory). An attribute is a chunk of metadata about a context. Contexts can have many attributes.
Some attributes may be large, for example a base 64 encoded version of the contexts content (133% context size). On the other hand an attribute can be small, for example the file size is exposed as an attribute.
Access to all contexts and attributes is performed by first requesting either an IStream or IOStream for that context or attribute. In this way the same context/attribute can be open many times at the same time, just like normal kernel based IO.
Ferris uses Loki from "Modern C++ Design" by Alexandrescu. Most objects use automatic garbage collection based on the SmartPtr template class from Loki. Where possible objects in ferris use a FerrisRefCounted policy to provide COM like intrusive reference counting. This style is used for Context, Attribute and special wrappers of IOStreams that are provided. IOStreams are wrapped to provide a more flexible API than could be offered using references to IOStreams.
There are also new stream classes provided, for example NullStream and LimitingStream. Templates are provided to make SmartPtrs to standard IOStreams act just like the underlying stream would, for example, one can have SmartPtr ss; ss >> stringObj; and does not have to dereference the SmartPtr to use standard IOStreams extractors or inserters.
Ferris uses GModule from glib2 to dynamically load both context and attribute classes at run-time. This way resources are conserved until they are needed. The native file system context is statically linked to ferris at present. When loading either contexts or attribute classes ferris uses a double dispatch factory method. Put simply this means that for each plugin there are two libraries, one that tells ferris if the main one really needs to be loaded or not. Using this scheme ferris can load all the meta factory classes at any time and use these very small meta factories to check if the main factory can create objects that are going to be useful.
This scheme is of great use for attribute classes. Attribute classes take a context and can "generate" attributes from the context. An example of this sort of class would be a MD5 or Base64 attribute. Both can be generated from the base context. More interesting attributes are PCM audio and RGBA-32bpp image data. By using the double dispatch factory ferris can handle a great deal of attribute generators and load them on demand.
Ferris currently can decode mp3, read id3 tags, decode many image formats and break some animation formats into frames. This makes ferris a solid starting point for multimedia applications.
Ferris will automatically mount sub file systems for you. Examples of a sub file system include a Berkeley database or XML file. For example it is possible to read a context such as /tmp/myxml.xml/mynode. Using this automatic mounting the differences between storage formats effectively disappear. To a ferris enabled application loading data from a native disk file, a Berkeley database, and XML file, or mbox file appear to be the same. This allows the user of the application to choose the correct storage for the data at hand.
It is planned to move to a microkernel architecture in Version 2.1 of ferris. I choose 2.1 so that ferris does not fall into version 2 syndrome.
Enhancements:
- Many changes were made to better support rsync(1).
- Extended Attribute support was greatly improved.
- write() now also updates mtime.

PythonCAD is a CAD package written, surprisingly enough, in Python. PythonCAD project aims to produce a scriptable, open-source, easy to use CAD package for Linux, the various flavors of BSD Unix, commercial Unix, and other platforms to which someone who is interested ports the program. Work began on PythonCAD in July, 2002, and the first public release was on December 21, 2002.

The twenty-fifth release of PythonCAD was made available May 26, 2005. This release fixes several compatibility issues found when running PythonCAD on PyGTK releseses prior than 2.4. Also, numerous changes to the event handling code have been applied to make the code better conform to GTK+/PyGTK conventions. Additionally a number of bug fixes and code improvements appear in this release as well.

Between the sixteenth and seventeenth releases of the program, the code was moved around internally to better cooperate with other Python programs. Unfortunately the Cocoa front-end code has suffered since then due to lack of maintainence and is currently not functional. Releases after the seventeenth release have attempted to improve the situation, but to no avail. A developer or team of developers running Mac OS X is needed to bring the Cocoa code into a usable state.