Free solution focused therapy software for linux

Content Area Focus is an extension used to solve the content area focus loss.

Target audience: those who are mostly using the keyboard to navigate around and switch between tabs; frequently they encounter situations in which the content area doesnt have focus.

Method: just giving focus to the content area for any "regular" keystrokes made when the main-window is in focus.

Flumotion project is a streaming media server created with the backing of Fluendo.
It features intuitive graphical administration tools, making the task of setting up and manipulating audio and video streams easy for even novice system administrators. Flumotion is released under the GPL.
Built upon proven and tested free software solutions
The Flumotion Streaming Server is built upon a platform of proven free software solutions. We have currently focused on the Linux platform for our main development. Flumotion is mainly written in the extremely popular Python language.
The high-level functionality is built on top of Twisted. The low-level functionality is built on top of GStreamer.
Wide hardware support
Due to the developers decision to focus on supporting the GNU/Linux operating system, we have support for a wide range of audio and video input devices supported by the operating system.
Flumotion currently supports streaming from webcams, TV capture cards, FireWire DV cameras and the OSS and ALSA sound systems.
Distributed design
Flumotion has a distributed design, making it easy to spread the load over multiple machines, allowing you to do advanced media manipulation and stream generation. No matter how many different streams or multiple versions of the same stream you want to do, or different formats, or overlays, Flumotion can easily scale to handle it by distributing the load onto serveral machines.
Commercial support
While Flumotion is a free software product using the widely accepted GPL license, it has the advantage of having a commercial company behind it. This means that if you introduce Flumotion into your company or organisation and you find you would like commercial support opportunities or extra functionality, there is an entity to turn to to have your need filled.
Setting up Flumotion
Depending on how you installed Flumotion, it will or will not be integrated with your distribution.
In this section we will cover configuring Flumotion on both types of systems. First we will explain how to start and run Flumotion when its not integrated with your distribution. These instructions also work on systems where its integrated, but its preferable to use the distribution-specific way of starting the server.
We also provide an example of running Flumotion on a system where it is integrated with the distribution through service scripts.
If you have received Flumotion packages from either Fluendo or your distribution, this type of integration should be available.
Flumotion on a system where it is not integrated
You are repsonsible yourself for providing a working configuration file, and starting the binaries.
Alternatively, we have also provided a service-like script called flumotion that provides some basic integration, much like a standard service script.
This script is installed in your sbin directory. You can list managers and workers configured, and start and stop them. Flumotion on a system where its integrated
In a well-configured system, Flumotion is integrated into the system using Unix service scripts. In this section, we use the Fedora Core installation of Flumotion as an example. Depending on your distribution, these instructions might slightly vary.
To start flumotion with the service scripts, you start it like any other service, by typing as root:
service flumotion start
which results in:
Starting manager default: [ OK ]
Starting worker default: [ OK ]
Configuration files for flumotion are stored under /etc/flumotion/. In that directory, there is one subdirectory for managers and one for workers. Under each of these, there is one directory with the name of the manager or worker, containing the relevant configuration information.
Typically, the managers directory contains a planet.xml file detailing general configuration for the manager, and a flows subdirectory containing all flows that should be loaded onto this manager.
By default, the installation of Flumotion only allows connections from the local host, for security reasons. If you want to allow other hosts to log in workers or administration clients, you should change the authentication settings and remove the host entries from planet.xml.
Enhancements:
- Minor feature enhancements

KToon is a 2D Animation Toolkit designed by animators (Toonka Films ) for animators, focused to the Cartoon Industry.
KToon is covered by the GPL License using G++, OpenGL and QT as programming resources from KDevelop as the development platform.
By now, KToon is only available for Unix systems but we expect to make it works on Windows systems too someday.

Autobuild project consists of a tool to process software build logs and generate HTML.
Autobuild is a package that processes output from building software, primarily focused on packages using Autoconf and Automake, and generates HTML summaries.
The output includes project name, version, build host types, build host name, and indication of success or failure.
The output is indexed in many ways to simplify browsing.
Enhancements:
- The tools now use cf-shell.sf.net instead of shell.sf.net.

LightZone is a proprietary photo browser and editor for Mac OS, Windows, and Linux. Its like Photoshop and The Gimp, but its easier to use and focused on photography.

LightZone photo editor features raw file support, high-fidelity color space management, color-managed printing and completely non-destructive editing

The Linux tarball is a complete binary including a manual and a Sun Java JRE. It requires no privileges and runs no install scripts.

LightZone is a proprietary photo editor developed by Light Crafts, Inc. of Palo Alto, CA.

Inferno is a compact operating system designed for building distributed and networked systems on a wide variety of devices and platforms.
Inferno was originally developed at Bell Labs (the research division of Lucent Technologies).
Inferno Operating System is a well-designed, economical operating system particularly suitable for use in networked devices such as advanced telephones, hand-held devices, TV set-top boxes, and many other embedded applications.
Inferno can run in native mode on an embedded system or in emulation mode under many different operating systems. Inferno has many features in common with Plan 9.
Cross-Platform Portability
Inferno can run as a user application on top of an existing operating system or as a stand alone operating system. Most of the popular operating systems and processor architectures are supported:
Host Operating Systems:
- Windows NT/2000/XP
- Irix
- Linux
- MacOS X
- FreeBSD
- Solaris
- Plan 9
Supported Architectures:
- Intel x86 (386 & higher)
- Intel XScale
- IBM PowerPC
- ARM StrongARM (ARM & Thumb)
- Sun SPARC
Inferno also runs as a plug-in under Internet Explorer version 4 and higher. Each Inferno system presents an identical environment to the applications, irrespective of the underlying host OS or architecture, allowing the developer to work with a truly homogeneous environment across multiple different platforms.
Portable Applications
Inferno applications are written in Limbo, a modern, safe, modular, concurrent programming language with C-like syntax. It is more powerful than C but considerably easier to understand and debug than C++ or Java. Limbo code is compiled into architecture independent byte code which is then interpreted (or compiled on the fly) on the target processor. This means that any Inferno application will run identically on all Inferno platforms.
Transparent Resources
Inferno offers complete transparency of resources and data using a simple but powerful namespace system. By representing resources as files and having one standard communication protocol, resources such as data stores, services and external devices can easily be shared between Inferno systems. A resource interface may be imported to the local system and used by the applications without them knowing, or needing to know, whether it is local or remote.
Security
High level security is an important part of the Inferno system. By using one standard protocol for all network communication, security can be focused on one point and provided at a system level. Inferno offers full support for authenticated, encrypted connections using a certificate based user identification scheme and variety of algorithms including:
- IDEA, 56 bit DES, 40, 128 and 256 bit RC4 encryption algorithms
- MD4, MD5 and SHA secure hash algorithms
A Complete Solution
Inferno is not only an operating system, it is also a complete development environment, providing all the tools necessary for creating, testing and debugging the applications that run within it.
- Acme IDE: includes editor, shell, advanced pattern matching tools & more
- Fast Compiler: with full syntax and compile time type checking
- Graphical Debugger: with full stack trace for currently executing threads
- Powerful Shell: with sophisticated scripting capabilities
- UNIX like commands: including bind, grep, gzip, mount, ps, tar, yacc...
Enhancements:
- New licence terms (a `dual licence scheme allowing use as Free Software)
- Styx revision based on 9P2000, and consequent changes to Sys
- Authentication changes
- Improved colour graphics support, including compositing
- Scalable fonts using Freetype
- Revamped Tk implementation
- Window management moved out of Tk to a separate window manager in Limbo
- Limbo: exception handling and fixed-point
- Limbo: other possible changes
- Dis VM changes
- More commands and library modules
- Better network service configuration
- /net/dns served by host and native DNS resolver
- Hosted kernels configured from a parts list as for native kernels
- Signed modules
- Internet Explorer plug-in revised and in source form
- Expanded documentation

Local Area Security is a research group focused on information security related subjects. We are most known for L.A.S. Linux. Our live-CD security toolkit.

Local Area Security is a project that was started in 2002 to research information security related topics. During that time there was no real live-CD toolkit focused on information security.

So Jascha, the project founder built one from a stripped down version of Knoppix called Model-K. Both of which were built from Debian Linux.

Up until version 0.4 L.A.S. Linux was command line only. Which made it limited to some of the tools it could contain since many require a GUI. Or at least for many it is preferable to have one. So FluxBox was added as the desktop since it is light weight and very feature filled.

It was during this time that Jascha came up with the idea of keeping the size of L.A.S. as small as possible, which lead to a target maximum size of 180MBs. The size of the original mini-CDs that were available at the time. This forced the selection of tools and features to be weighed heavily since unlike other live-CDs that throw in everything including the kitchen sink. L.A.S. was designed from the ground up to be a tool not a all-inclusive grab bag of applications.

As well as many advances for live-CDs came about, such as to-ram that allows booting a live-CD into the physical RAM of a computer. Which by chance L.A.S. was perfectly cut out for. With as little as 256MB of RAM people could boot L.A.S. and then free up their CD-ROMs for burring etc.

For forensics this was a big plus, along with many other uses. Plus L.A.S. ran very fast in RAM which helped with running Nessus, Nmap, or other tools. When compared to full size (700MB) CDs which would require 1GB of RAM to use the to-ram option, it was really no contest.