Free avalon harvest software for linux

Harvest is a system to collect information and make them searchable using a web interface. Harvest can collect information on inter- and intranet using http, ftp, nntp as well as local files like data on harddisk, CDROM and file servers.
Current list of supported formats in addition to HTML include TeX, DVI, PS, full text, mail, man pages, news, troff, WordPerfect, RTF, Microsoft Word/Excel, SGML, C sources and many more. Stubs for PDF support is included in Harvest and will use Xpdf or Acroread to process PDF files. Adding support for new format is easy due to Harvests modular design.
Harvest is a modular, distributed search system framework with a working set components to make it a complete search system.
Main features:
- Harvest is designed to work as distributed system. It can distribute the load among different machines. It is possible to use a number of machines to gather data. The fulltext indexer doesnt have to run on the same machine as broker or web server.
- Harvest is designed to be modular. Every single step during collecting data, and answering search requests are implemented as single programs. This makes it easy to modify or replace parts of Harvest to customize its behaviour.
- Harvest allows complete control over the content of data in the search database. It is possible to customize the summarizer to create desired summaries which will be used for searching. The filtering mechanism of Harvest allows to make modifications to the summary created by summarizers. Manually created summaries can be inserted to the search database.
- The Search interface is written in Perl to make customization easy, if desired.
Enhancements:
- src/common/qdbm: updated to qdbm-1.8.20.
- components/broker/zebra/yaz: merged yaz-2.0.30.

Pax Logging is a consolidation effort that aims to make all existing logging APIs in the Java world available for OSGi developments, driven by a Log4J backend.
Each legacy API is loaded as its own bundle. The logging service can be reloaded at run-time.
Main features:
- Log4J driving the backend implementation.
- Log4J API supported.
- Jakarta Commons Logging API supported.
- Pax Logging Service implements the standard OSGi Log Service API.
- JDK Logging API support.
- Avalon Logger API support.
- SLF4J API support.
- Knopflerfish Log service support.

The Virtual Data Center (VDC) is a digital library system "in a box" for numeric data.

The VDC is a web application which provides everything necessary to maintain and disseminate collections of research studies: including facilities for the storage, archiving, cataloging, translation, and dissemination of each collection.

It includes on-line analysis, powered by the R Statistical environment. It also provides extensive support for distributed and federated collections including: location-independent naming of objects, distributed authentication and access control, federated metadata harvesting, remote repository caching, and distributed virtual

GalaxyHack project allows you to design a fleet of spaceships which can then be tested in AI script based battles against fleets designed by other players.

Though battles take place in real time, the strategy comes before hand, both in writing short AI scripts in a simple scripting language, and also in the set up and selection of your fleet.

You dont actually have any control over your units at all mid-battle, but rather use the time to see where the set up of your fleets is working, where your fleets weaknesses lie and changes are needed, and perhaps also to learn from the strategy of your opponent.

The game revolves around very large capital ships, from which smaller ships are launched, but which are not designed for attacking themselves, and which cannot be moved mid-battle. To win a battle you must destroy of all of your opponents capital ships before they destroy yours.

There can be hundreds of units in any one battle, but there is no harvesting, resource management or base building.

Fleet customisation:

There are three basic unit types: capital ships, frigates and small ships. All three are customisable with a small range of different weapons and technologies. Fleet selection and unit customisation are done using a windows-and-menus based editor. Each fleet has a points value, which is increased by adding or upgrading units.

You are able to save a fleet, along with a corresponding set of AI script selections.

AI scripting:

A "group" of units - consisting of up to three actual units - has an AI script attached to it. Scripts are written using a simple proprietary language. There are two generic types of weapons in the game: "small" and "big". "small" weapons are always fired automatically when there is an enemy within range, whilst "big" weapons are fired on the basis of AI script commands. The game translates the AI commands for a group into commands for each individual unit within that group.

AI scripts are written externally to the game using any program capable of editing text files.

The chief principle of GalaxyHack AI scripts is "If this then that else the other". For a more concrete example, here are two lines of code from an AI file:

if aenemy type == smallship health < 100
move nenemy type == smallship health < 100

Scripts also support:

* function calls
* a variety of different sorts of variables which can have their value changed by scripts.

Multiplayer:

The game is designed to allow different commanders to test their fleets in battle against one another. Up to four fleets can participate in any one battle. This said, the game is not properly "multiplayer" in that you never actually play in real time against other players. Instead, you can download fleets designed by other players from an online database. You are encouraged to submit your own fleets to this database for other players to download and battle against.

Graphics and sound:

The game engine is a 2D affair, with ships and what have you shuffling about. It is fairly easy to create your own custom art for your units, should you so wish.

There are various basic graphical effects for firing weapons of various sorts, units being destroyed, etc.

The game features music composed by The Embryo.

The game does not feature any sound effects.

BW whois is a modern whois client that works as a full-featured Web application or as a commandline tool. BW whois is flexible and configurable with self-detecting CGI support, multiple security options in the CGI mode, a mature TLD table, database caching (using MySQL or PostgreSQL), and many more options and features
Main features:
- Self-detecting CGI support
- Simple command-line use
- Prevents data harvesting with multiple security features for web use
- Optional result caching with an SQL database
- Database features work with either MySQL or PostgreSQL
- Support for multiple outgoing IP addresses
- Support for available/not available results
- Fully customizable HTML output
- Support for Apache-style SSI (server-side includes)
- External TLD table for support of ALL top-level domains
- Fully configurable disclaimer stripping
- Automatic support for netblocks
- Unpacks packed (single-integer) IP addresses
Enhancements:
- Multiple outgoing IP addresses are supported to help with whois servers that block based on queries per IP address.
- Support was added for PostgreSQL in addition to MySQL for database features.
- Support for mod_perl was improved, and support for non-standard whois servers (like whois.denic.de) was improved.

NewsBro project is a web application providing usenet news service. It provides support for multiple users accessing multiple news groups via multiple news servers.
Main features:
- web-based Usenet access
- full-featured news reader
- multi-user access with individual profiles
- one click filtered access to all images within a newsgroup
- multi-server binary file support
- XFace support
- yEnc decoder
- stand-alone and Java servlet versions
- News RC File
- Header and article caching
- NZB support
- XPAT threading
- Binary file harvesting
- Watch List for monitoring followups
- RSS feed for each group
- Configurable threads list

HTMLParser is a super-fast real-time parser for real-world HTML. What has attracted most developers to HTMLParser has been its simplicity in design, speed and ability to handle streaming real-world html.
The two fundamental use-cases that are handled by the parser are extraction and transformation (the syntheses use-case, where HTML pages are created from scratch, is better handled by other tools closer to the source of data). While prior versions concentrated on data extraction from web pages, Version 1.4 of the HTMLParser has substantial improvements in the area of transforming web pages, with simplified tag creation and editing, and verbatim toHtml() method output.
In order to use HTMLParser you will need to be able to write code in the Java programming language. Although some example programs are provided that may be useful as they stand, its more than likely you will need (or want) to create your own programs or modify the ones provided to match your intended application.
To use the library, you will need to add either the htmllexer.jar or htmlparser.jar to your classpath when compiling and running. The htmllexer.jar provides low level access to generic string, remark and tag nodes on the page in a linear, flat, sequential manner. The htmlparser.jar, which includes the classes found in htmllexer.jar, provides access to a page as a sequence of nested differentiated tags containing string, remark and other tag nodes. So where the output from calls to the lexer nextNode() method might be:
< html>
< head>
< title>
"Welcome"
< /title>
< /head>
< body>
etc...
The output from the parser NodeIterator would nest the tags as children of the , and other nodes (here represented by indentation):
< html>
< head>
< title>
"Welcome"
< /title>
< /head>
< body>
etc...
The parser attempts to balance opening tags with ending tags to present the structure of the page, while the lexer simply spits out nodes. If your application requires only modest structural knowledge of the page, and is primarily concerned with individual, isolated nodes, you should consider using the lightweight lexer. But if your application requires knowledge of the nested structure of the page, for example processing tables, you will probably want to use the full parser.
Extraction
Extraction encompasses all the information retrieval programs that are not meant to preserve the source page. This covers uses like:
- text extraction, for use as input for text search engine databases for example
- link extraction, for crawling through web pages or harvesting email addresses
- screen scraping, for programmatic data input from web pages
- resource extraction, collecting images or sound
- a browser front end, the preliminary stage of page display
- link checking, ensuring links are valid
- site monitoring, checking for page differences beyond simplistic diffs
There are several facilities in the HTMLParser codebase to help with extraction, including filters, visitors and JavaBeans.
Transformation
Transformation includes all processing where the input and the output are HTML pages. Some examples are:
- URL rewriting, modifying some or all links on a page
- site capture, moving content from the web to local disk
- censorship, removing offending words and phrases from pages
- HTML cleanup, correcting erroneous pages
- ad removal, excising URLs referencing advertising
- conversion to XML, moving existing web pages to XML
During or after reading in a page, operations on the nodes can accomplish many transformation tasks "in place", which can then be output with the toHtml() method. Depending on the purpose of your application, you will probably want to look into node decorators, visitors, or custom tags in conjunction with the PrototypicalNodeFactory.
The HTML Parser is an open source library released under GNU Lesser General Public License, which basically says you are free to use the library "as is" in other (even proprietary) products, as long as due credit is given to the authors and the source code for the HTMLParser is included or available with the other product. For modified or embedded use, please consult the LGPL license.