Free facilitates software for linux

FastFormat 0.4.2 offers users a brilliant and flexible tool functioning as a C++ output/formatting library. FastFormat does not suffer from the common problems that plague standard and third-party libraries: lack of type-safety, lack of speed, lack of I18N/L10N support.

Hackystat is a framework for the automated collection and analysis of software engineering product and process data.
Hackystat uses sensors to unobtrusively collect data from development environment tools; there is no chronic overhead on developers to collect product and process data. Hackystat does not tie you to a particular tool, environment, process, or application.
Hackystat project is intended to provide in-process project management support.
Hackystat is in its sixth major architectural release family. The first architectural release family, called the "Spike Solution", was used to explore the feasibility of the approach and to evaluate various component technologies (including JATO, XSL, Ant, JUnit/HttpUnit, Tomcat, Cocoon, and SOAP). Work on this Spike Solution architecture lasted eight months, from May to December, 2001.
In December 2001, we began a major re-implementation of the system in order to provide architectural support for design discoveries made with the Spike Solution. This second architectural release family is called the "Framework Architecture", because it implements package and class-level patterns that facilitate extension of the system via inheritance and composition of existing classes. Unfortunately, the Framework architecture required modification of the hackystat source code to implement new sensors and analysis, and only a single configuration of analyses and sensors can be supported in this architecture.
In November, 2002, we began work on the "SDK" (or "kernelized") architecture release family. This third architectural family decomposes the system into two layers. The first layer is a kernel system which implements the core facilities for data definition, storage, transmission and user interface.
Developers build an actual Hackystat installation by combining the framework with a second layer: a set of plug-in extension modules that define the specific sensor data types, tool sensors, and analyses required to support their development procedures. In the SDK architecture, developers can implement new sensors and analyses without modifying the underlying kernel code, and multiple Hackystat installations can be built with different configurations of analyses and sensors.
In June, 2003, we performed a package restructuring that facilitates the development of third layer, or "application" layer systems. This is the fourth architectural release family, called the "Three Layer" architecture.
After only a month of application layer development, we realized that the build process we developed for the second release family would be woefully inadequate to support the three layer architecture, in which multiple components would be combined into a configuration for release.
So, in August, 2003, we released the fifth architectural release family, called the "Component Architecture", along with extensive new build support including the hackydev web site with daily integration builds.
In July, 2004, we released the sixth architectural family, which provides services to support a "telemetry" based approach to software project monitoring and control. This includes various caching mechanisms, as well as the hackyTelemetry package that includes a telemetry specification language and associated APIs. In this architecture, telemetry support becomes a "low level" feature of the system.
Enhancements:
- A new sensor for IntelliJ Idea, enhancements to the Visual Studio sensor, improved support for test driven development inference, and many bugfixes.

iriverter is a cross-platform frontend to mencoder designed to facilitate the conversion of almost any video format to one that is playable on various multimedia players. It can convert almost any video format to one that is playable on various multimedia players, like the iRiver H320, H340, PMP120, PMP140, U10, iAudio X5 and iPod Video.
Enhancements:
- Update clix / U10 profile
- Better defaults for X5
- Added Zen Vision:M profile (thanks Mat Sheehan)
- Added logging to diagnose problems easier (Help->Log Viewer)
- Simplified conversion code
- Fixed black and white wmv conversions
- Installer now optionally installs codecs like Real and Windows Media
- Support for iPod Video (not enabled yet)

UserTracking 2 is a tool that works closely together with Radiator and 802.1x in an attempt to facilitate forensics investigations. It does this by linking network layer 2 (i.e. MAC addresses) to network layer 3 (i.e. IP addresses).
Since 802.1x keeps logs of users and MAC addresses while forensics investigations will typically have an IP address and a timestamp of an offense, it is necessary to have such a link between layer 2 and layer 3.
Enhancements:
- Easily installable Debian packages are now available.

PaiPix Linux is a compilation of Free Software, based on KNOPPIX live linux, that is meant to be used in any environment but with special emphasis on science and technologies.
PaiPix Linux should provide an open door to the public including not only the tolls used by the scientists but also the best free applications that make your computer more interesting for any usage.
If you like it for office, video or even gaming, who knows if someday you can get curious and give a look at the scientific applications that are in your DVD.
PaiPix can be used at home, in medium and even large size organizations where the sharing of the compressed DVD image and the included afs file system support make it extreemely powerfull.
PaiPix Linux also serves to support clusters of distributed computing (using the paipix-terminalsever), for data servers, farms simulation farms and user laboratories.
PaiPix linux combines all the versatility of KNOPPIX with optimized configuration for several languages, including Portuguese. It intends to not only serve in document editing tasks but also for advanced technological and scientific systems.
Using the paipix-remaster script, you can change the default language of your iso image or add your personal files to the PAIPIX DVD.
This work was only possible because Free Software experts have created all the infrastructure allowing a gigantic world-wide community of software volunteers develop what is already, without any doubt, the best operative system the world.
However, because (r)evolutions take time, many companies that are developing systems - which in the end are designed to store in practice the technological and scientific knowledge of mankind - still work in a closed form (proprietary).
There is still a reason to use other operative systems while the community of free software does not this knowledge to the whole humanity. In the following table we include a correspondence that facilitates the migration to free software for each application. All mentioned free software is installed in PaiPix!
This software is distributed without any guarantee if not the fact that a great number of components are permanently being used and tested by millions of people in the whole world.
Based on Knoppix 3.8, including kernel 2.6.11. It uses the Unionfs file system that mounts the DVD image in read-write mode. Using this feature, PAIPIX can run your 3D-enabled drivers for ATI or NVIDIA cards. Just use knoppix install=ati or knoppix install=nvidia as boot option and run the FlightGear simulator (fgfs) to see the new fantastic 3D support in Linux
Enhancements:
- The new PAIPIX 7 keeps its focus on scientific software but drops the emphasis on a pure live DVD to integrate installation, live and upgrade systems. The new main use cases are: LIVE - starting PAIPIX in the live mode, one has access to complete system including KDE, office and development; INSTALLATION - by starting PAIPIX in the installation mode one has access to the standard Debian installer system; UPGRADE - as part of the entire system, the DVD includes a Debian CD-ROM repository that includes all necessary packages. The PAIPIX ISO images are available in English and in bilingual editions that support both English and one of the following languages: Portuguese, Spanish, French, Italian and German.

Funambol is open source mobile application server software that provides push email, address book and calendar (PIM) data synchronization, application provisioning, and device management for wireless devices and PCs, leveraging standard protocols. For users, this means BlackBerry-like capabilities on commodity handsets.
This project is also a software development platform for mobile applications. It provides client and server side Java APIs, and facilitates the development, deployment and management of any mobile project. Funambol is the de facto standard implementation of the Open Mobile Alliance Data Synchronization and Device Management protocols (OMA DS and DM, formerly known as SyncML).
Main features:
- Funambol Data Synchronization Server: a mobile application server providing synchronization services for wireless clients and PCs, including push email.
- Funambol Device Management: an OMA DM server to remotely manage mobile devices.
- Funambol Connectors: gateways to file systems, databases, email systems, and applications for two-way synchronization with existing data assets.
- Funambol Client Plug-ins: protocol extenders and clients for Outlook, Windows Mobile, BlackBerry, Palm and iPod so users can synchronize their email messages and PIM data (address book, calendar, tasks and notes) with the server.
- Funambol Software Development Kit: tools to develop sometimes-connected mobile applications on devices (in Java - J2SE and J2ME - and C++) and to add data sources to the server.
Enhancements:
- Major feature enhancements

Rocks Cluster is a complete "cluster on a CD" solution for x86 and IA64 Red Hat Linux COTS clusters.
Building a Rocks cluster does not require any experience in clustering, yet a cluster architect will find a flexible and programmatic way to redesign the entire software stack just below the surface (appropriately hidden from the majority of users).
Although Rocks includes the tools expected from any clustering software stack (PBS, Maui, GM support, Ganglia, etc), it is unique in its simplicity of installation.
From a hardware component and raw processing power perspective, commodity clusters are phenomenal price/performance compute engines. However, if a scalable ``cluster management strategy is not adopted, the favorable economics of clusters are offset by the additional on-going personnel costs involved to ``care and feed for the machine. The complexity of cluster management (e.g., determining if all nodes have a consistent set of software) often overwhelms part-time cluster administrators, who are usually domain application scientists. When this occurs, machine state is forced to either of two extremes: the cluster is not stable due to configuration problems, or software becomes stale, security holes abound, and known software bugs remain unpatched.
While earlier clustering toolkits expend a great deal of effort (i.e., software) to compare configurations of nodes, Rocks makes complete Operating System (OS) installation on a node the basic management tool. With attention to complete automation of this process, it becomes faster to reinstall all nodes to a known configuration than it is to determine if nodes were out of synchronization in the first place. Unlike a users desktop, the OS on a cluster node is considered to be soft state that can be changed and/or updated rapidly.
This is clearly more heavywieght than the philosophy of configuration management tools [Cfengine] that perform exhaustive examination and parity checking of an installed OS. At first glance, it seems wrong to reinstall the OS when a configuration parameter needs to be changed. Indeed, for a single node this might seem too severe. However, this approach scales exceptionally well, making it a preferred mode for even a modest-sized cluster. Because the OS can be installed from scratch in a short period of time, different (and perhaps incompatible) application-specific configurations can easily be installed on nodes. In addition, this structure insures any upgrade will not interfere with actively running jobs.
One of the key ingredients of Rocks is a robust mechanism to produce customized distributions (with security patches pre-applied) that define the complete set of software for a particular node. A cluster may require several node types including compute nodes, frontend nodes file servers, and monitoring nodes. Each of these roles requires a specialized software set. Within a distribution, different node types are defined with a machine specific Red Hat Kickstart file, made from a Rocks Kickstart Graph.
A Kickstart file is a text-based description of all the software packages and software configuration to be deployed on a node. The Rocks Kickstart Graph is an XML-based tree structure used to define RedHat Kickstart files. By using a graph, Rocks can efficiently define node types without duplicating shared components. Similiar to mammalian species sharing 80% of their genes, Rocks node types share much of their software set. The Rocks Kickstart Graph easily defines the differences between node types without duplicating the description of their similarities. See the Bibliography section for papers that describe the design of this structure in more depth.
By leveraging this installation technology, we can abstract out many of the hardware differences and allow the Kickstart process to autodetect the correct hardware modules to load (e.g., disk subsystem type: SCSI, IDE, integrated RAID adapter; Ethernet interfaces; and high-speed network interfaces). Further, we benefit from the robust and rich support that commercial Linux distributions must have to be viable in todays rapidly advancing marketplace.
Wherever possible, Rocks uses automatic methods to determine configuration differences. Yet, because clusters are unified machines, there are a few services that require ``global knowledge of the machine -- e.g., a listing of all compute nodes for the hosts database and queuing system. Rocks uses an SQL database to store the definitions of these global configurations and then generates database reports to create service-specific configuration files (e.g., DHCP configuration file, /etc/hosts, and PBS nodes file).
Enhancements:
- Rocks v4.3 is released for i386 and x86_64 CPU architectures. New features: Rocks command line - initial release of the Rocks command line which facilitates non-SQL administrative access to the database; PXE First - hosts can now be configured in BIOS with a boot order of CD, PXE, hard disk. Enhancements: based on CentOS 4.5 and all updates as of July 4, 2007; Anaconda installer updated to 10.1.1.63; performance improvement when building torrent files for the Avalanche Installer; database indirects, more flexibility with Rocks variables; Globus updated to gt4.0.4 with web services....

Mail::Message::Field contains one line of a message header.

INHERITANCE

Mail::Message::Field
is a Mail::Reporter

Mail::Message::Field is extended by
Mail::Message::Field::Fast
Mail::Message::Field::Flex
Mail::Message::Field::Full

SYNOPSIS

my $field = Mail::Message::Field->new(From => fish@tux.aq);
print $field->name;
print $field->body;
print $field->comment;
print $field->content; # body & comment
$field->print(*OUT);
print $field->string;
print "$fieldn";
print $field->attribute(charset) || us-ascii;

This implementation follows the guidelines of rfc2822 as close as possible, and may there produce a different output than implementations based on the obsolete rfc822. However, the old output will still be accepted.

These objects each store one header line, and facilitates access routines to the information hidden in it. Also, you may want to have a look at the added methods of a message:

my @from = $message->from;
my $sender = $message->sender;
my $subject = $message->subject;
my $msgid = $message->messageId;

my @to = $message->to;
my @cc = $message->cc;
my @bcc = $message->bcc;
my @dest = $message->destinations;

my $other = $message->get(Reply-To);