Free distributed version control system software for linux

Distributed Access Control System is a complete, light-weight, single sign-on and role-based access control system distributed under an open source license. It provides:
- extended authentication and role-based access control capabilities for Apache-based web services, CGI programs, and virtually any program or script;
- a wide array of flexible, modular, and efficient authentication methods, including two-factor authentication and hardware tokens;
- powerful, rule-based authorization checking that can be applied transparently to any resource or activity (such as web services, web content, and program features) by Apache-based web services and CGI programs, or virtually any program or script;
- an Apache 2.0/2.2 module, suite of CGI programs, and collection of command line tools for Unix-type platforms, such as Linux, FreeBSD, and Solaris.
Enhancements:
- This release includes an important bugfix to local_passwd_authenticate that prevents invalid passwords from being accepted.
- Some minor bugs have also been addressed, including some problems with dacs.quick(7).

Distributed Concurrent Versioning System (DCVS) project extends the well-known version control system CVS and the file distribution and synchronization program CVSup with functionality to distribute CVS repositories with local lines of development and handle synchronization of the distributed repositories automatically in the background.
Development lines (branches) are owned by a repository server, repository servers efficiently update each other via CVSup, and CVS ensures correct server use on checkin and branch creation.
Enhancements:
- This release adds miscellaneous bugfixes and the security patches of CVS 1.12.13.
- There are now installation packages for Windows to be installed on Cygwin, for SUSE Linux 10, for FreeBSD 4, 5, and 6, and for Fedora Core 4.

Distributed Multi-User Compilation System is a system that allows a group of users to share a compilation farm. Each compilation request from each user will be sent to the fastest available machine, every time.
Main features:
- Supports multiple users compiling simultaneously, and scales well to handle the new loads.
- Supports multiple operating systems in the compilation farm.
- Uses all processors of a multi-processor compilation host.
- Makes best use of compilation hosts with widely differing CPU speeds.
- Guarantees that a compilation host will not be overloaded by compilations.
- Takes into account the load on a host caused by non-compilation tasks.
- Supports the dynamic addition and removal of hosts to the compilation farm.
- Works with distcc, which need not be altered in any way.
DMUCS consists of these (main) programs:
- dmucs: the "host-server". This application reads a configuration file indicating the number of CPUs and the "power" of each potential host in the compilation farm. It then receives over the network:
- load average information from each compilation host.
- host requests from compile tasks that need remote hosts on which to run.
- information requests from monitoring applications.
- status requests from an administrator.
- dmucs maintains the database of hosts in the compilation farm, and assigns hosts to compilation tasks, giving out the best host/cpu available when the compilation task asks.
- gethost: a compilation task uses gethost get a host/cpu from the dmucs server. In general, a makefile will perform a compilation this way:
- gethost distcc gcc ...
- gethost contacts the server to get a host, which it puts into the environment variable DISTCC_HOSTS. gethost then calls the program given to it. After that program ends, gethost releases the assigned host back to the dmucs server.
- loadavg: the administrator of the compilation farm must start this application on each compilation host. loadavg sends the load average of the compilation host to the dmucs server periodically. The dmucs server will "downgrade" a compilation host if the hosts load averages goes too high.
- monitor: the administrator (or anyone) may use this program to monitor the busy-ness of the compilation farm. It displays which hosts/cpus are available in the compilation farm, which hosts/cpus have compilation tasks assigned to them, which hosts have been made administratively unavailable, and which hosts are "silent" - i.e., the dmucs server has not received a load average message from the compilation host for a while.

Coda is an advanced networked filesystem. The project has been developed at CMU since 1987 by the systems group of M. Satyanarayanan. in the SCS department.
Coda is a distributed filesystem with its origin in AFS2. It has many features that are very desirable for network filesystems. Currently, Coda has several features not found elsewhere.
1. disconnected operation for mobile computing
2. is freely available under a liberal license
3. high performance through client side persistent caching
4. server replication
5. security model for authentication, encryption and access control
6. continued operation during partial network failures in server network
7. network bandwith adaptation
8. good scalability
9. well defined semantics of sharing, even in the presence of network failures
Enhancements:
- Coda now works on 64-bit systems.
- The client and server were successfully built and used on a machine with em64t extensions with a 64-bit Linux kernel.
- The new RVM-1.14 and RPC2-2.5 releases also incorporate some essential 64-bit fixes.
- Another welcome change is that venus now tries to keep cached access rights available for users even across system reboots or client restarts, which should improve life for people who frequently shut down or dual boot their machines.

The Distributed Hardware Evolution Project allows the distribution of a genetic algorithm evolving hardware designs across the Internet by setting up an island on each clients PC which will evolve during idle time. Individuals from these islands will migrate between each other as they compete for survival.

All source code is available at Sourceforge under the projects named JaGa, DistrIT, and IslandEv. The source code is generalizable to any genetic algorithm or distributed processing task.

Distributed FTP is a distributed FTP daemon written in java. Instead of usual and well-known serversclient transfer it uses masterclient for control connections and slaveclient for (most) data transfers, the master must tell the slave to initiate/respond to a transfer.

Distributed Checksum Clearinghouse, in short DCC, is a system of clients and servers that collect and count checksums related to mail messages. The counts can be used by SMTP servers and mail user agents to detect and reject bulk mail.
DCC servers can exchange common checksums. The checksums include values that are "fuzzy", or constant across common variations in bulk messages.
Enhancements:
- This release improves the dccifd per-user whitelist default.
- It fixes the server database size estimate.
- Old installations really should upgrade to get the MIME decoding fix.

Superversion is a multi-user distributed version control system based on change sets. It aims to be an industrial-strength, open source alternative to commercial solutions that is equally easy to use (or even easier) and similarly powerful. In fact, intuitive and efficient usability has been one of the top priorities in Superversions development from the very beginning.
If youre frustrated with CVS - as so many developers before you - and dont want to spend money on a version management software, try Superversion today! Superversion is ublished under the GPL and free to use even in commercial environments.
Main features:
- Very easy download, installation and setup in just a few clicks
- Platform-independent; supported on Windows, Linux, OS/2, OpenVMS (should run on Macs too - feedback welcome!)
- Graphical user interface for all operations
- Fully transactional internal database - very strong protection against data loss
- Can be used with any editor or file-based IDE
- Compressed diff view for every file accessible in just one click
- Instant overview of all new/changed/deleted files in work area
- Changes can be collected in a buffer before being committed to repository
- Branching
- Branch merging
- All file changes stored as diffs (low space consumption even for binary files)
- Report functions: fulltext search, state comparison, file history
- Support for multiple work areas per project (simultaneous work on different versions)
- Graphical project history view
- Keyword replacement (analogous to CVS)
- Convenient selection of files and directories to be ignored
- Marker system to assign human-readable labels to versions
- Comments assignable to every version, every file
- Export of any recorded version as zip file, complete directory or file-wise
- File type (binary/text) detected automatically (manual override possible)
- Help text in most dialogs
Enhancements:
- The user interface is faster and more responsive in many places.
- There is a new dialog for adding work areas.