Free twisted sister i wanna rock software for linux

Twisted Packager II (TP2) is a package manager that aims to make live easy - for end users and also developers. In some respects it is similar to Autopackage - it does not intend to replace the "system packaging tool" but instead will sit alongside it to allow application developers an easy way to package software; and system administrators an easy way to install [or remove!] such software.
TP2 excels at handling generic software - and allows a "source" type package [such as itself!] to be installed across multiple architectures and operating systems using the same package.
TP2 is cross-platform; it is currently in use on Solaris, Linux and HP-UX. Soon the intention is validate it also for BSD and AIX.
TP2 is flexible. It supports dependency management, package verification, preview installation and removal, and audit logs all activity.
TP2 is powerful. It supports "namespaces" which allows the same packages to be installed into different areas on the same machine. Non-root users can be given areas which they can manage independently.
Enhancements:
- Initial public announcement, though the software has been in use in several environments for over 12 months.

Twisted Storage is an application that will take your data and manage it for you, just like a file system. But Twisted Storage goes way beyond what a normal file system does.
What types of "objects" are stored in Twisted Storage : just regular files. The data stored in the system is expected to be fixed content, meaning it doesnt change at all. If you read the data back, change it, and store it, it is considered a different file. There are plenty of examples of fixed content data : emails you received, movies or mp3 files you made or own, documents you wrote, etc. In fact it is estimated that 80% of the data you have on your computer is fixed, reference data.
Your Twisted Storage system can start out small - a single computer with a few disk drives. When you need more storage you can add more disk drives and more computers. But it has been designed to store petabytes worth of data without requiring any special hardware. For example storing a petabyte worth of data, using the biggest disk drives available today (500 GB), would require 2000 disk drives. To overcome the need of special hardware, Twisted Storage is a scalable, distributed system using ordinary commodity computers. Even so that petabyte of data would require 500 computers networked together and that requires special handling.
Twisted Storage has a few features you wont find in any file system. For example once a file is added to the Twisted Storage repository it can be written in multiple locations simultaneously. The system has been designed to be compliant with Sarbanes-Oxley Act: when an object is added to the repository you can no longer delete it and the integrity of the contents are guaranteed. In addition any access to the object is recorded.
Main features:
Scalable to thousands of servers and multiple petabytes of data.
- Regardless of how much data you want to store,Twisted Storage is designed to handle it. The system can grow from one computer and a few disks to hundreds of systems and thousands of disk drivers.
Automatic data recovery without human intervention.
- Twisted Storage doesnt require backup/restore software or procedures. All data written to the system is recorded in multiple locations.
No special disaster recover procedures.
- So long as you have your systems in physically different locations and you have instructed the software to write the multiple copies to those systems, you have no-hassle disaster recover. If one of the sites goes down, the system will retrieve any data from the other systems. Additionally, once the disaster site is up and running, the system will automatically restore the data to the it.
Simplified configuration.
- To ease management of the system, you can change any one systems configuration and have it ripple through out the system.

TwistedJava provides an implementation of the Perspective Broker protocol in Java.
TwistedJava is an LGPLed implementation of the Perspective Broker protocol for Java. PB is a remote object protocol, similar to RMI, supporting multiple programming languages.
Included is a policy (Straw) written by Brandon Wiley that lets you use remote Java objects transparently.
You can read the README for the latest version, or read the API javadocs.
Enhancements:
- Adds support for logging in to Twisted 1.1 PB servers.

Twisted Words library provides implementations of a handful of IM protocols, including IRC, MSNP8, OSCAR, TOC, and Jabber.

Twisted Words provides two separate high-level end-user features:

a multiprotocol instant messaging server
a multiprotocol instant messaging client

These are both still in the early stages of development and are not expected to work flawlessly in all configurations, however each is quite usable for a limited set of functionality. A Twisted Words server can be created with just a couple commands:

$ mktap words --irc-port 6667 --pb-port 8787 --passwd password_file --group somegroup
$ twistd -f words.tap

The Twisted Words client is named im and is usable as an IRC client, and possibly an AIM client (depending on the phase of the moon).

Low Level Functionality:

Twisted Words also includes:

Low-level protocol implementations of OSCAR (AIM and ICQ), IRC, MSN, TOC (AIM).
Jabber libraries.

Prototypes of chat server and client frameworks built on top of the protocols.

Twisted is a framework, written in Python, for writing networked applications. Twisted includes implementations of a number of commonly used network services such as a web server, an IRC chat server, a mail server, a relational database interface and an object broker.
Developers can build applications using all of these services as well as custom services that they write themselves. Twisted also includes a user authentication system that controls access to services and provides services with user context information to implement their own security models.
Main features:
- Pluggable event loops allowing the developer to take advantage of platform-specific capabilities.
- Abstractions of protocols and transports.
- Through Twisted Spread, mechanisms for network encoding of data (in Python, Java, ELisp, and other languages), to a full-blown distributed object system.
Twisted is an integration point for network services that were previously unable to interoperate. Services within a Twisted server can communicate with each other and share information providing a very integrated programming environment that can re-use large amounts of infrastructure across multiple network mediums (such as chat, web, and mail).
As well as servers, Twisted supports several different kinds of clients and GUIs. This means that the client can re-use large portions of the servers code, improving test coverage and reliability while reducing code size.
Twisted is a collection of servers and clients, which can be used either by developers of new applications or directly.
Enhancements:
- This release includes many fixes for UDP and multicast stdio on Win32.
- Many bug fixes were made for Trial, and its support for a large number of previously deprecated APIs was dropped.
- Deferred Generators no longer leak their final result or exception.
- LoopingCall now supports functions which return Deferreds.
- A cooperative scheduler with pluggable policies has been added.
- Much of the API documentation has been improved and a new guide for developing producers and consumers has been added.
- This also includes new releases of Conch, Mail, Names, Words, and Web.

Thinking Rock project is a Java based software application for collecting and processing your thoughts, following the GTD methodology.
Thinking Rock allows you to collect your thoughts and process them into actions, projects, information or future possibilities. Actions can be done by you, delegated to someone else or scheduled for a particular date. Projects can be organised with ordered actions and sub-projects. You can review all of your actions, projects and other information quickly and easily to see what you need to do or to choose what you want to do at a particular time.
Main features:
- It will help you to store in one safe place all the things you have to do or would like to do one day;
- Unlike many task management applications, Thinking Rock lets you to group your actions in projects and sub-projects;
- It gets you moving on your thoughts by encouraging you to think of the next physical action to take;
- It is simple, easy (help documentation provided) and quick to use ;
- We provide free customer support;
- The data file is separate so you can have the application installed on your home computer and at work, and transfer the small data file between computers;
- It is multi-platform: use it on Linux, Machintosh, or Windows;
- Its free.

NowListening is just a simple NowListening script for Kopete.

Usage:

Simply run the script. First time it will ask you for a default name, pic and how do you want to show your name while playing. In case you have Kopete closed it will open it up for you.

HOWTO for display name:

%artist: for showing current artist.
%album: for showing current album.
%title: for showing current title.
%track: for showing current track number.
%genre: for showing current genre listening.

For example: "Alex (%artist - %track because %genre rules!)" will show
Alex (the Doors - Peace Frog because Rock rules!)

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....