Free native american names software for linux

Twisted Names project is both a domain name server as well as a client resolver library.
Twisted Names comes with an "out of the box" nameserver which can read most BIND-syntax zone files as well as a simple Python-based configuration format.
Twisted Names can act as an authoritative server, perform zone transfers from a master to act as a secondary, act as a caching nameserver, or any combination of these.
Twisted Names client resolver library provides functions to query for all commonly used record types as well as a replacement for the blocking gethostbyname() function provided by the Python stdlib socket module.
Twisted Names is available under the MIT Free Software licence.
Enhancements:
- Errors in the markup used in API documentation have been fixed.
- A bug where the DNS client would sometimes drop a response has been fixed.
- A bug which prevented non-IN lookups from generating malformed queries has been fixed.

Active Calendar is PHP Class, that generates calendars (month or year view) as a HTML Table (XHTML-Valid). Active Calendars source code is free.
You can modify or pass it on under the conditions of the GNU Lesser General Public License, published by the Free Software Foundation.
The calendars created by this class:
can be static (without any links)
can optionally have navigation controls
can optionally have a date picker control
can optionally have linkable days (url or javascript)
can optionally have event days with event links and own layout
can optionally have event content with links and own layout
support different GMT zones for the current date calculation
support month and day names, depending on your language
can be configured using CSS
do not require Javascript to be displayed or navigated (server side generation)
can be generated with just 2-3 lines of code
Active Calendar is based on the PHP native date functions (default) and supports optionally the ADOdb Date Library. Supported dates (on systems using a 32-bit signed integer Unix time_t):
Using PHP native date functions: 1902 - 2037 (UNIX) and 1971 - 2037 (Windows)
Using ADOdb Date Library: 100 - 3000 and later [ limited by the computation time of adodb_mktime() ] on both UNIX and Windows. To use the ADOdb Date Library just include it in your scripts. The Active Calendar class will use the library functions automatically.
Enhancements:
- An activeCalendarWeek subclass was added.
- The class can generate week calendars (one or multiple rows) according to the date or the week number of the year passed to the class using two public methods, showWeeks() and showWeeksByID().
- The structure of the download package was updated and an example was added for demonstrating how the Active Calendar can be used as a popup date selector in a form.

American Political Science: Campaign Simulator project is a statistically based political campaign simulation game.
The Campaign Simulator is an attempt to statistically model and predict the outcome of an American presidential election.
Several users assume the roles of competitive candidates and inflict the repercussions of certain decisions on a GSS-based dataset.
The application is written in Java and supports all operating systems with a Java 1.5 VM.
Main features:
- Time is not the only limiting variable. In fact, time may not be the proper limit as most operations may be performed in tandem; an economic system that allows fund raising elements should be implemented.
- The current choices all utilize the same dataset algorithm to effect the populace in similar ways- this set of scripts should be broadened and deepened as they are too high level.
- The Python Architecture needs polishing- the internal IDE is not complete, and the ability to assign scripts to run at differing points in the lifetime of the application has yet to be created.
- The installer should place links on the desktops of Mac and Unix/Linux Systems.
- Some of the small features planned, such as a GUI for dialog creation, have been cut for the deadline and should be added.

CentOS is an Enterprise-class Linux Distribution derived from sources freely provided to the public by a prominent North American Enterprise Linux vendor.
CentOS conforms fully with the upstream vendors redistribution policy and aims to be 100% binary compatible. (CentOS mainly changes packages to remove upstream vendor branding and artwork.) CentOS is free, however, we ask for a small contribution. CentOS is a project of the cAos Foundation.
CentOS is developed by a small but growing team of core developers. In turn the core developers are supported by an active user community including system administrators, network administrators, enterprise users, managers, core Linux contributors and Linux enthusiasts from around the world.
CentOS has numerous advantages over some of the other clone projects including: an active and growing user community, quickly rebuilt, tested, and QAed errata packages, an extensive mirror network, developers who are contactable and responsive, multiple free support avenues including IRC Chat, Mailing Lists, Forums, a dynamic FAQ. Commercial support is offered via a number of vendors.
CentOS exists to provide a free enterprise class computing platform to anyone who wishes to use it. CentOS 2 and 3 are fully compatible rebuilds of RHEL 2 and 3 respectively. CentOS 2 and 3 are reproduced from RHEL sources that are freely distributed by RedHat.
Redistributed packages and sources comply fully with RedHats redistribution requirements. CentOS 2 and 3 are designed for people who need an enterprise class OS without the cost, support, certification, or brand name of RedHat.
Main features:
- easy maintenance
- suitability for long term use in production environments
- friendly environment for users and package maintainers
- long-term support of the core
- active development
- community infrastructure
- open management
- open business model
- commercial support - offered by a partner vendor
Enhancements:
- OpenOffice.org 2.0.4
- Firefox 1.5.0.10
- Thunderbird 1.5.0.10
- Gaim-2.0.0
- Scribus-1.3.3
- xchat-2.6.6
- k3b-0.12.17
- Gimp-2.2.13

IAM OPML Parser Class parses an OPML file (provided its URL) and returns an array.

OPML (Outline Processor Markup Language) is an XML format for outlines. Originally developed by Radio UserLand as a native file format for an outliner application, it has since been adopted for other uses, the most common being to exchange lists of web feeds (RSS) between web feed aggregators. The OPML specification defines an outline as a hierarchical, ordered list of arbitrary elements. The specification is fairly open which makes it suitable for many types of list data.

The XML elements in an OPML document are:

< opml version=”1.0″ > This is the root element. It must contain the version attribute and one head and one body element. Currently, there’s active work in OML 2.0, which is mainly aimed at solving some of v1.o’s shortcomings.

< head > Contains metadata. May include any of these optional elements: title, dateCreated, dateModified, ownerName, ownerEmail, expansionState, vertScrollState, windowTop, windowLeft, windowBottom, windowRight. Each element is a simple text element. dateCreated and dateModified contents conform to the date-time format specified in RFC 822. expansionState contains a comma-separated list of line numbers that should be expanded o and size of the display window. An OPML processor may ignore all the head sub-elements. If the outline is opened inside another outline then the processor must ignore the window elements.

< body > Contains the content of the outline. Must have one or more outline elements.

< outline > Represents a line in the outline. May contain any number of arbitrary attributes. Common attributes include text and type. The outline element may contain any number of outline sub-elements. While there are many tools to create and/or read OPML files, there are few PHP libraries/functions to work with these files.

This PHP class parses an OPML file (provided its URL) and returns an array with all the parsed data. This array contains, for each of the OPML file’s elements the following attributes: link_url, link_name, link_target, link_description, link_rss, created (date of creation), type (link type: RSS, HTML, etc.). The class uses file_get_contents() to retrieve the contents of the OPML file and then the XML extension is used to parse and store the file’s data in an associative array, where each outline element is stored using a different array index. The array has the following structure:

0 : Array:
{
names => Preface
urls => http://www.php.net/manual/en/preface.php
targets =>
feeds =>
descriptions =>
created => Nov 28 2005 21:05:49 GMT
type => link
}
1 : Array:
{
names => I. Getting started
urls =>
targets =>
feeds =>
descriptions =>
created =>
type =>
}

DNS name parser is a Java utility library for parsing dns names, ip and hw addresses.

Synopsis

import su.netdb.parser.*;

Parser parser = new Parser();

Hashtable result = parser.parse(str);

System.out.println("string: "+result.get("string"));
System.out.println("hw: "+result.get("hw"));
System.out.println("name: "+result.get("name"));
System.out.println("domain: "+result.get("domain"));
System.out.println("ip_low: "+result.get("ip_low"));
System.out.println("ip_high: "+result.get("ip_high"));

"DNS name parser" is an utility library created to be used in a search application. Given a single input field its function is to differentiate between several types of possible input strings. Namely if it a dns name, IP address (exact, ip range or ip with wildcards) or hardware address. The result of the parsing is a Hashtable with possible keys "string", "hw", "name", "domain", "ip_low" and "ip_high".

Steel Bank Common Lisp is a development environment for Common Lisp, with excellent support for the ANSI standard: garbage collection, lexical closures, powerful macros, strong dynamic typing, incremental compilation, and the famous Common Lisp Object System (multimethods and all).

Steel Bank Common Lisp also includes many extensions, such as native threads, socket support, a statistical profiler, programmable streams, and more. These are all available through an integrated, interactive native compiler which feels like an interpreter.

SBCL is unique in being a multiplatform native compiler which bootstraps itself completely from source, using a C compiler and any other ANSI Common Lisp implementation.

Whats New in This Release:

* enhancement: experimental macro SB-EXT:COMPARE-AND-SWAP provides
atomic compare-and-swap operations on threaded platforms.
* enhancement: experimental function SB-EXT:RESTRICT-COMPILER-POLICY
allows assining a global minimum value to optimization qualities
(overriding proclamations and declarations).
* enhancement: closed over variables can be stack-allocated on x86
and x86-64.
* performance bug fix: GETHASH and (SETF GETHASH) are once again
non-consing.
* optimization: slot definition lookup is now O(1). This speeds up
eg. SLOT-VALUE and (SETF SLOT-VALUE) with variable slot names.
* optimization: STRING-TO-OCTETS is now up to 60% faster for UTF-8.
* optimization: ASSOC and MEMBER can now be open-coded for all
combinations of keyword arguments when second argument is constant
and SPEED >= SPACE. In other cases a specialized version is
selected.
* bug fix: using obsoleted structure instances with TYPEP and
generic functions now signals a sensible error.
* bug fix: threads waiting on GET-FOREGROUND can be interrupted.
(reported by Kristoffer Kvello)
* bug fix: backtrace construction is now more careful when making
lisp-objects from pointers on the stack, to avoid creating bogus
objects that can be seen by the GC.
* bug fix: defaulting of values in contexts expecting more than 7
variables now works on x86-64. (reported by Christopher Laux)
* bug fix: modifications to packages (INTERN, EXPORT, etc) are now
thread safe.
* bug fix: (SETF SYMBOL-PLIST) no longer allows assigning a non-list
as the property-list of a symbol.
* bug fix: DEFMETHOD forms with CALL-NEXT-METHOD in the method body,
in EVAL-WHEN forms with both :COMPILE-TOPLEVEL and :LOAD-TOPLEVEL
situations requested, are once again file-compileable. (reported
by Sascha Wilde)

XML::DB::DatabaseManager is an approximation to the XML:DB DatabaseManager.

SYNOPSIS

use XML::DB::DatabaseManager;
my $driver = Xindice; my $url = http://localhost:4080;
eval{ $dbm = new XML::DB::DatabaseManager(); $dbm->registerDatabase($driver); $col = $dbm->getCollection("xmldb:$driver:$url/db/test"); ...... };
if ($@){ die $@; }
deregisterDatabase($driver);

This is the initial class to use to get access to the XML:DB modules, an approximate implementation of the XML:DB API defined for Java at http://www.xmldb.org. This implementation is designed to give a uniform Perl access over XML-RPC to both of the current free native XML databases, eXist and Xindice, as well as providing the same front-end for a plain file-system.

Unlike the DatabaseManager defined in the XML:DB API (which is a Factory), this simply registers driver names, generating a new Database instance for each request. Multiple database drivers can be used simultaneously (eg. to transfer data from one database to another). The drivers themselves are rather confusingly called Databases in this system.

Only one DatabaseManager can be instantiated in a program.