Free run multiple operating systems software for linux

DragonFly is an Linux operating system and environment designed to be the logical continuation of the FreeBSD-4.x OS series. These operating systems belong in the same class as Linux in that they are based on UNIX ideals and APIs. DragonFly is a fork in the path, so to speak, giving the BSD base an opportunity to grow in an entirely new direction from the one taken in the FreeBSD-5 series.

It is our belief that the correct choice of features and algorithms can yield the potential for excellent scalability, robustness, and debuggability in a number of broad system categories. Not just for SMP or NUMA, but for everything from a single-node UP system to a massively clustered system. It is our belief that a fairly simple but wide-ranging set of goals will lay the groundwork for future growth.

The existing BSD cores, including FreeBSD-5, are still primarily based on models which could at best be called strained as they are applied to modern systems. The true innovation has given way to basically just laying on hacks to add features, such as encrypted disks and security layering that in a better environment could be developed at far less cost and with far greater flexibility.

We also believe that it is important to provide API solutions which allow reasonable backwards and forwards version compatibility, at least between userland and the kernel, in a mix-and-match environment. If one considers the situation from the ultimate in clustering... secure anonymous system clustering over the internet, the necessity of having properly specified APIs becomes apparent.

Finally, we believe that a fully integrated and feature-full upgrade mechanism should exist to allow end users and system operators of all walks of life to easily maintain their systems. Debian Linux has shown us the way, but it is possible to do better.

DragonFly is going to be a multi-year project at the very least. Achieving our goal set will require a great deal of groundwork just to reposition existing mechanisms to fit the new models. The goals link will take you to a more detailed description of what we hope to accomplish.

1.2.0 is our second major DragonFly release and the first one which we have created a separate CVS branch for. DragonFlys policy is to only commit bug fixes to release branches.

This release represents a significant milestone in our efforts to improve the kernel infrastructure. DragonFly is still running under the Big Giant Lock, but this will probably be the last release where that is the case.

The greatest progress has been made in the network subsystem. The TCP stack is now almost fully threaded (and will likely be the first subsystem we remove the BGL from in coming months). The TCP stack now fully supports the SACK protocol and a large number of bug and performance fixes have gone in, especially in regard to GigE performance over LANs.

The namecache has been completely rewritten and is now considered to be production-ready with this release. The rewrite will greatly simplify future filesystem work and is a necessary precursor for our ultimate goal of creating a clusterable OS.

This will be last release that uses GCC 2.95.x as the default compiler. Both GCC 3.4.x and GCC 2.95.x are supported in this release through the use of the CCVER environment variable (gcc2 or gcc34). GCC 2.95.x is to be retired soon due to its lack of TLS support. The current development branch will soon start depending heavily on TLS support and __thread both within the kernel and in libc and other libraries. This release fully supports TLS segments for programs compiled with gcc-3.4.x.

It goes without saying that this release is far more stable then our 1.0A release. A huge number of bug fixes, performance improvements, and design changes have been made since the 1.0A release.

DesktopBSD aims at being a stable and powerful operating system for desktop users.
DesktopBSD combines the stability of FreeBSD, the usability and functionality of KDE and the simplicity of specially developed software to provide a system thats easy to use and install.
The main goal of the DesktopBSD project is to provide a desktop operating system thats easy to use, but still has all the functionality and power of BSD.
In the long term, DesktopBSD wants to build an operating system that meets most requirements desktop users have, like installing software, configuring power management or sharing an internet connection.
To be better able to fulfill this goal, we strongly rely on users that send in feature requests, ideas for improvements or participate in development.
DesktopBSD is free software, which means it is free of charge. Also, if youre a developer and want to find out how DesktopBSD works or modify it to fit your needs, you can download the full source code.
Main features:
Stability
- DesktopBSD is based on FreeBSD, which is one of the most reliable and robust operating systems in the world.
Usability
- The KDE Desktop Environment and specially developed tools provide a maximum of usability to our users. KDE features such as KIO slaves or remote desktop sharing and DesktopBSD features like network profiles, easy mount procedures and many other convenience features make life easier and increase productivity.
Performance
- The development of FreeBSD (and therefore DesktopBSD) is highly focused on performance. The system manages resources efficiently and reacts fast even when many processes are running simultaneously. This also affects networking, so DesktopBSD tries to optimally use the available bandwidth.
Security
- Concerning security, the BSD operating systems are world-class. For example, OpenBSD had only one remote in the default install in more than eight years. DesktopBSD benefits from the work of other BSDs such as OpenBSD and passes that advantage on to you.
Enhancements:
- This release candidate is considered a large step towards a final release 1.6 with major changes such as: X.Org release 7.2, improving support for modern graphics hardware; NVIDIA graphics driver, providing hardware 3D acceleration for NVIDIA video cards; Latest FreeBSD 6-STABLE as base system with High Definition Audio (HDA) support... Upgrades from 1.0 and previous release candidates are supported. An additional language CD and 64-bit (AMD64) DVD will be released soon.

Koch-Suite is a PHP-based recipe management system for Unix-like operating systems. It uses MySQL or PostgreSQL as database backends. The project is licensed under a BSD-style (three-clause) license and therefore it is Open Source.
Tested and supported are currently the operating systems Linux, OpenBSD and FreeBSD. The Koch-Suite should run on other operating systems, too, it just isnt tested so far.
Enhancements:
Webinterface:
- A pastebox for easy recipe import
- tagging of recipes for merged operations (printing, export, deleting ...) in one round.
- Editing of categories (delete, merge,...)
- Rating system
- Plenty beautifications (Themes!).
- New export format: REZKONV
- Countless bugs have been fixed.

Libvirt is a C toolkit to interact with the virtualization capabilities of recent versions of Linux (and other OSes). It is free software available under the GNU Lesser General Public License.
Virtualization of the Linux Operating System means the ability to run multiple instances of Operating Systems concurently on a single hardware system where the basic resources are driven by a Linux instance.
Libvirt aim at providing long term stable C API initially for the Xen paravirtualization but should be able to integrate other virtualization mechanisms if needed.
Enhancements:
- Support for secure remote access to nodes was added.
- Many bugfixes and documentation improvements were made.

XChat is an IRC (chat) program for Windows and UNIX (Linux/BSD) operating systems. I.R.C. is Internet Relay Chat, see http://irchelp.org for more information about IRC in general.
XChat runs on most BSD and POSIX compliant operating systems.
Main features:
- Full featured IRC client
- Fully customizable
- Tabbed window interface
- Small resource footprint
- 41 language translations
- encrypted connections using OpenSSL 0.9.8d
- native IPv6 support
- Perl, Python, Ruby and Tcl language interface plugins for scripting

The Prex project is an open source initiative to provide a portable real-time operating system for embedded systems.
This project originally started to make a royalty-free OS for mobile phones and PDA in order to spread open source movement to such proprietary OS field. And now, the project target has been shifted to the wider area of real-time and embedded systems.
Prex is designed specifically for small memory footprint platforms. It is written in C language based on traditional micro-kernel architecture. The Prex kernel provides only fundamental features for task, thread, memory, ipc, exception, and synchronization.
The other basic OS functions, process, file system, application loading, and networking, are provided by the user mode servers. In addition, Prex provides a POSIX emulation layer in order to reuse the existing applications.
Prex is an open source royalty-free OS for mobile phones and PDA.
This design allows system to perform both of the native real-time task and the generic *NIX process simultaneously without degrading the real-time performance. Furthermore, it helps the platform designer to construct OS by choosing suitable server tasks for their target requisition.
Prex is royalty-free software released under BSD License
Main features:
- Task and thread control: preemptive priority scheduling with 256 priority levels
- Memory management: virtual address mapping, shared memory, memory protection, with MMU
- IPC: synchronous message passing among threads, object name space in kernel
- Exception: framework for POSIX signal emulation
- Synchronization: semaphores, condition variables, and mutexes with priority inheritance
- Timers: sleep timers, alarm timers
- Interrupt: nested interrupt service routines, and prioritized interrupt service threads
- Device I/O: minimum synchronous I/O interface
- Real-time: low interrupt latency, high resolution timers, periodic timers, and scheduling quantum control
- Cross platform portability: well defined architecture dependent layer and driver-kernel interface
- Modular design: OS servers and BSP module separated from kernel
- Small memory footprint: kernel size < 25k bytes
- Low power consumption: control of processor idle state, support of DVS (Dynamic Voltage Scaling)
- Disk-less: on-core kernel, no memory page swapping
- Instantly available: minimal OS boot time, system suspend/resume, kernel warm restart
- File systems: VFS framework, RAM/FAT/Flash file systems optimized for embedded systems
- Networking: TCP/IP stack, BSD socket interface
- POSIX emulation: signal, process, file I/O, real-time extensions, pthread, etc
- Debug: event logging, GDB remote debug
Enhancements:
- A file system server was added. arfs, devfs, and ramfs are supported with this version.