Free thin software for linux

Thinux is a thin client system that resides on a Red Hat Linux server. When a thin client requests to boot on LAN, the server will upload the thin client linux system to the thin client. Ideal for lightweight devices such as Point-of-Sales terminals, embedded devices, etc.

PeeWeeLinux is an ongoing development effort to provide an environment that makes the configuration and installation of a Linux operating system on an embedded platform as easy and painless as possible.
Main features:
- Developed on a RedHat 6.2 platform
- Packages build and maintained using rpm
- Packages are customized to minimize memory footprint
- Ncurses driven graphical configuration and installation tools
- 2.2.x kernel enhanced for embedded applications
- USB support
- PCMCIA support
- XFree86 support
The configuration utility is menu driven and allows for complete packages, or a subset of files from packages, to be included in the target system. Target system using syslinux or lilo bootloaders are supported.
Targets can consist of root ramdisks, read-only root partitions and conventional single read-write root partitions. Projects can be saved for later use; thus making it very easy to test several different configurations.
PeeWeeLinux includes a complete and growing assortment of utilities and applications for a variety of products. Custom configuration files and binaries can be added to a project and saved with a project.
Possible applications for systems build with PeeWeeLinux include:
- Rescue floppy disks
- Routers
- Firewalls
- Thin-Clients
- much more
The PeeWeeLinux kernel sources include a number of important features for embedded applications; like GPL compliant drivers for flash devices, the latest available network drivers, USB and PCMCIA support.
PeeWeeLinux as a whole is distributed under the GPL license. Individual packages and components are licensed per their respective owners.

X/OS Linux is derived from the Free/Open Source rpm packages of Red Hat Enterprise Linux 4 (RHEL4) under the requirements set forth by their trademark policy.

X/OS has spent considerable effort to avoid using Red Hats trademarks in any way that would imply an association with or sponsorship by Red Hat.

After some delay, the final release of X/OS Linux 4.0 is now available to the public.

The X/OS Linux team has spent considerable effort to assure the label enterprise-grade Linux for this milestone release. With the simultaneous availability of X/OS Linux 4.0 for x86 and x86_64 processor architectures, it delivers the latest “best-of-breed” Free and Open Source software for both 32- and 64-bit platforms.

Highlights include the 2.6 Linux kernel featuring numerous enhancements over the previous 2.4 version, Security Enhanced Linux (SELinux) to apply more granular security policies, improved storage capabilities supporting file systems of up to 8TB and more.

The Global File System (GFS) and Cluster Suite software is included in this release to ease the task of creating and managing advanced cluster configurations, and is available as an extra option during installation. This powerful set of tools provides seamless scalability of applications such as databases, web servers and high-performance computing clusters — with GFS enabling nodes to simultaneously read and write to a single shared filesystem.

Next to providing an advanced server platform, X/OS Linux 4.0 adds various enhancements to the desktop — increasing usability with greatly improved office productivity tools, plug-and-play USB device recognition and power management supporting the ACPI standard.

In addition to compatibility with the de facto distribution for deploying Linux in the enterprise, X/OS Linux strides to include various other useful packages and tools that conform to the standard for mature and robust “enterprise-grade” software. One example is Xfce, an extra option in addition to Gnome and KDE, offering a light-weight desktop environment suited for use on low-end or thin client systems.

The purpose of the SurakWare Base Library (SWL/libswl) is to serve as a platform independent development framework for C++ and QPascal.
The SWL includes both thin layers over functionality exposed by the Linux and Windows operating systems as well as higher level classes for many purposes. Save for a few exceptions, the SWL is completely indpedenent from the STL and the C/C++ runtime library.
Platform independence has been achieved by encapsulating OS-specific implementation details in a number of SWL classes. There should never be a need to use "#ifdef"s to distinguish between platforms.
Enhancements:
- Some memory and file descriptor leaks were fixed.
- Some buffer indexing problems were fixed. I/O dispatcher problems on high load notifies were fixed.
- TFile::directory() was fixed.
- TEventManagers add/remove operation logic was improved.
- TNullEnumerator::moveNext() was fixed so that it returns false rather than throwing an exception.
- Some 64-bit vs. 32-bit compilation fixes were made.
- TStream::readTimeout and writeTimeout were backported from trunk to 0.4 (and thus introduced EIOTimeout exception).
- General improvements were made to TArgumentEvaluator and TAnsiColor.
- General code cleanup was done.

MetaTheme is a project dedicated to unification of appearance between
different graphics toolkits, such as GTK and QT.
The program is designed as a thin layer between toolkits and theme engines, creating unified API by which each theme engine can draw. The result is that every application uses the same code for drawing, making the appearance same across different applications. MetaTheme also adjusts behaviour a bit, so the overall effect of unification is impressive.
Some applications have their own toolkits which are used only by themselves. Cardinal examples of such applications are Mozilla, Firefox and OpenOffice. They provide support for pixmap themes, and popular themes exists for them.
Though as they are pixmap based, you cant easily change how they look. Particularly, its quite impossible to change color theme. Not everyone likes the default. Also, the behaviour of these toolkits is unaffected, so the application may behave differently than other applications.
There is planned support for Firefox (and maybe Mozilla too) in future. For
OpenOffice, you can at least try the KDE integration build of it.
Main features:
- supported toolkits:
- GTK2
- QT/KDE
- Java/SWING
- theme engines:
- Redmond 2000
- Plastik
- Plastik XP
- Industrial
- Flat
- easy installation

Pluto is the Reference Implementation of the Java Portlet Specfication. The current version of this specification is JSR 168.
Portlets are designed to run in the context of a portal. They are written to the Portlet API which are similar to the Servlet API.
In contrast to servlets, portlets may not do things like sending redirects or errors to browsers directly, forwarding requests or writing arbitrary markup to the output stream to assure that they don?t distract the portal web application which uses them.
Another difference compared to servlets is that portlets rely on portal specific infrastructure functions such as access to user profile information, standard interface for storing/retrieving persistent settings, getting client information, etc. Generally,
portlets are administrated more dynamically than servlets typically are.
A portlet container provides a runtime environment for portlets implemented according to the Portlet API. In this environment portlets can be instantiated, used and finally destroyed. The portlet container is not a stand-alone container like the servlet container; instead it is implemented as a thin layer on top of the servlet container and reuses the functionality provided by the servlet container.
Pluto serves as portlet container that implements the Portlet API and offers developers a working example platform from which they can test their portlets. However, its cumbersome to execute and test the portlet container without a driver, in this case, the portal.
Plutos simple portal component is built only on the portlet containers and the JSR 168s requirements. (In contrast, the more sophisticated, Jetspeed project concentrates on the portal itself rather than the portlet container, and considers requirements from other groups.)
Enhancements:
- Added Pluto 1.1 index page and basic documentation
- PLUTO 164: response contentType can change after getWriter()
- PLUTO 155: URL encoding in pluto 1.0.1-RC4 issue when using apache with jk2
- PLUTO 157: portlet.tld taglib is using jsp version 1.1. JSR168 spec requires JSP version 1.2
- PLUTO 152: Support maven deployment to a remote repository
- PLUTO 130: portlet:namespace fails inside JSTL c:set
- PLUTO-107: Admin portlet fails to add page. Hot deployment now supported.
- PLUTO-92: Deployer strips elements from web.xml (Deploy War Portlet)

DungeonMaker-Lib is a fork of the project DungeonMaker, which has been abandoned. A fork was chosen as changes needed to be made to the original code to more easily accommodate scripting front-ends. The code forks from their 2.02 release.
This C++ library "grows" dungeons for use in isometric games using artificial life algorithms. It is a fork of the existing DungeonMaker project, which has been abandoned.
Desiring to create a Perl front-end to the library, I decided to fork as I wanted to make some changes to the code itself.
The code is forked from their v2.02 release. The major change in the current release is the incorporation of the original main.cpp into the DungeonMaker object itself as a new generate() method.
This makes it much easier to develop front-ends. Further changes are forthcoming. Soon the Swig interface file and Perl front-end will be added to the release with other interfaces hopefully to follow.
This project is brand-new and thus the website and other documentation is somewhat thin, but will expand over time.
Enhancements:
- All changes from the DungeonMaker-Lib fork were merged with the main DungeonMaker tree.
- A preliminary Perl front-end was released.