Free 1400s in architecture software for linux

Af-Arch is being developed to give GNU/Linux a new middle-ware for building enterprise managing applications, typically database oriented.
Af-Arch is a complete set of libraries and tools which allows to develop distribuited system especially designed to face problems about bussiness applications.
Actually, Af-Arch is really robust and stable, having systems installed on many environments. Af-Arch, at this moment, runs on GNU/Linux and Microsoft Windows.
AF Architectures license schema is based on GPL and LGPL, allowing you to develop not only open source applications but also comercial applications without any royalty or fee.
Af-Arch is a strongly documented project, which is proved to work. Af-Arch keeps on evolving and growing its feature list allways keeping in mind productivity.
Enhancements:
- A new major stable release have come with many interesting features, library dependencies news, new API to make life easy and a bunch of work to make the library to be memory efficient.
- Af-Arch no longer depends on GDA library (http://www.gnome-db.org). Now AfGs, server side support for Af-Arch, includes built-in database abstraction support, implemented to fit better with the Af-Arch framework. For more details check the "libafgs" log below.
- Af-Arch platform now support three new return types: AfDalNodeData, AfDalStringData and AfDalDecimalData, which allows services to return a module node, a plain string and a decimal value as a result for the invocation.
- Af-Arch now support a new formal parameter service AfDalSetOf which implements set of items to be sent while the service is invoked.
- af-gen tool now support defining string literals that are separated by "+" sign, making it easy to write long SQL sentences.
- af-gen tool now allow to generate type definitions that could extend, making it possible to create a class hierarchy for types to be returned by services.
- libafdal core library now implements a better error reporting mechanism which allows to receive all errors generated while performing invocation at the reply process code.
- New reserved services have been added: element_peek_reference which allows to get the node associated to a module which is relationed through the 0..1 link.

An open Quality of Service Architecture is an open architecture for the provisioning of Quality of Service related functionality into the Linux kernel.
The project features a flexible, portable and lightweight software architecture for supporting QoS related services on the top of a general-purpose operating system as Linux. The architecture is well founded on formal scheduling analysis and control theoretical results.
At the core of the software there is an adaptive Resource Reservation layer that is capable of dynamically adapting the CPU allocation for QoS aware applications based on its run-time requirements.
As it is highlighted by the AQuoSA architecture, the project is mainly composed of two components:
- the QoS Res module, for which you can browse online the kernel, application and internal APIs
- the QoS Mgr module, for which you can browse online the kernel, application and internal APIs
Enhancements:
- Some bug fixed

Adaptive Quality of Service Architecture (AQuoSA) is an open architecture for the provisioning of adaptive Quality of Service functionality into the Linux kernel. The project features a flexible, portable, lightweight and open architecture for supporting soft real-time applications with facilities related to timing guarantees and QoS, on the top of a general-purpose operating system as Linux.
At the core of the architecture there is an adaptive resource reservation layer that is capable of dynamically adapting the CPU allocation for QoS aware applications based on their run-time requirements.
Timing guarantees are provided through an in-kernel reservation based process scheduler, whose services are exposed to applications through a well-designed API.
A supervisor performs admission control, so that admitting into the system new applications with timing guarantees does not affect the timing guarantees of already admitted applications. Also, it takes care of guaranteeing appropriate security policies in the assignment of timing guarantees to users and user groups, as configured by the system administrator.
A feedback-based QoS control layer may be optionally used by applications who want to keep their timing guarantees by using a CPU allocation that is continuously adapted according to their actual needs. This leaverages the programmer, within certain limits, to hard-code any particular reservation amount within the application, because the best allocation is found out automatically at run-time. Also, this enhances the possibilities for the system to host additional QoS controlled applications. The available control algorithms are well founded on formal scheduling models and control theoretical results.
Enhancements:
- This release introduces a couple of flags useful when creating servers. If QOS_F_PERSISTENT is enabled, a server is allowed to exist beyond detach of the last task. If QOS_F_SOFT is enabled, a server tasks are scheduled by the Linux default scheduler/policy, when outside of the server reservation.
- Also, various stability issues in destroying servers have been fixed, also thanks to a new release of the generic scheduler patch for the Linux kernel (gs-2.2).

IRC Collective software contains a parser, with a modular architecture that makes it flexible in the way it can process input and handle output. The output of the parser is primarily used to add to an SQL database that can in turn be queried by, e.g., a Web application (also provided).

The parser can be extended by defining new input formats and output handlers. It can help you stay up to date on the IRC channels that you visit regularly. You can write your own applications on top of the SQL database. You can search past conversations using the Web interface (results will be paged).

Lazy TSS's I/O bitmap update 0.2 provides you with an excellent product which implements a lazy TSSs I/O bitmap copy for the i386 and x86-64 architecture.

Instead of copying the bitmap at every context switch, the TSSs I/O bitmap offset is set to an invalid offset, so that an attempt to access the bitmap from the CPU will trigger a GP fault. It is lazily at that stage that the bitmap is updated, by hence avoiding bitmap copies in cases where the switched task do not perfom any I/O operation.

Adaptive Quality of Service Architecture (AQuoSA) is an open architecture for the provisioning of adaptive Quality of Service functionality into the Linux kernel. The project features a flexible, portable, and lightweight software architecture for supporting QoS-related services on top of a general-purpose operating system as Linux.

The architecture is well founded on formal scheduling analysis and control theoretical results. At the core of the architecture there is an adaptive resource reservation layer that is capable of dynamically adapting the CPU allocation for QoS aware applications based on their run-time requirements.

Timing guarantees are provided through an in-kernel reservation based process scheduler, whose services are exposed to applications through a well-designed API.

A supervisor performs admission control, so that admitting into the system new applications with timing guarantees does not affect the timing guarantees of already admitted applications. Also, it takes care of guaranteeing appropriate security policies in the assignment of timing guarantees to users and user groups, as configured by the system administrator.

A feedback-based QoS control layer may be optionally used by applications who want to keep their timing guarantees by using a CPU allocation that is continuously adapted according to their actual needs. This leaverages the programmer, within certain limits, to hard-code any particular reservation amount within the application, because the best allocation is found out automatically at run-time. Also, this enhances the possibilities for the system to host additional QoS controlled applications. The available control algorithms are well founded on formal scheduling models and control theoretical results.

Software::Packager is a common software packaging interface.

SYNOPSIS

use Software::Packager;
my $packager = new Software::Packager();
$packager->version(1.2.3.4.5.6);
$packager->package_name("Somename");
$packager->program_name(Software Packager);
$packager->description("This is the description.");
$packager->short_description("This is a short description.");
$packager->output_dir("/home/software/packages");
$packager->category("Applications");
$packager->architecture("sparc");

my %object_data = (
SOURCE => /source/file1,
TYPE => file,
DESTINATION => /usr/local/file1,
USER => joe,
GROUP => staff,
MODE => 0750,
);
$packager->add_item(%object_data);

my $version = $packager->version();
my $name = $packager->package_name();
my $program_name = $packager->program_name();
my $description = $packager->description();
my $description = $packager->short_description();
my $output_directory = $packager->output_dir();
my $category = $packager->category();
my $arch = $packager->architecture();

The Software Packager module is designed to provide a common interface for packaging software on any platform. This module does not do the packaging of the software but is merely a wraper around the various software packaging tools already provided with various operating systems.

This module provides the base API and sets default values common to the various software packaging methods.