Free virtual earth software for linux

Virtual Cron is a PHP library that can check whether it is time to run a periodical task. The class can be used to check whether it is time to run a task that must run from time to time.

It creates a control file to keep track the last time the task was scheduled.

The class can check the control file last modification time to determined whether it passed a given period of time since the last time the task was run.

If the given interval time has passed since the last run, the class recreates the control file and returns true to inform the application that is time to run the task again.

Virtual Collaboratory is a directed discussion forum based on Mailman and Smartarchiver that provides for threaded short and long term discussions.
Virtual Collaboratory includes a calendaring function, integratation with the Elluminate meeting software, document exchange, version control, a research resource center, custom categorizations, FAQs, and the ability to search for users with similar interests.
Enhancements:
- Refactored Plone into three separate products
- Better Elluminate integration
- I18N support via Py-MYCMSs traslate functionality
- Refactored smartarchiver as a py-mycms system
- Easier isntallation through Install Constancts
- Front page Alerts
- BlogPoster blog management system (works with your blog to help groups collaborate on blog content)
- No longer requires specially patched versions of Zope & plone. (Authentications now done through the PyMyCMSUserFolder)
- Virus checking (pyclamav) now supported if pyclamav is installed

Virtual Drum Machine is a simple drum machine.
It works for little endian/linux kind of machines. You may let it work on others machines, but you probably will get troubles with it.
You definitely need oss (or maybe alsa) for sound output, and a posix-like operating system. To let it work on a big endian machine should be painful.
You write a rhythm, then you compile it, then you are able to play it to your sound card or save it to a file.
The Virtual Drum Machine is made of
- the Rhythm Compiler,
- the runtime library.
The Virtual Drum Machine is in the public domain. Who needs a license? money makers? Protection against robbery? let me laugh... Read any text of law, you will see where the robbers reside.
A simple file would look like :
void main_rhythm(void)
{
tempo = 120;
- a
. b
. b
.
- a
.b
- a
.
. b
. b
- a c
. b
}
Install:
Do a "./configure" in the drums directory, then "make", then "make install", it should be alright. You can listen to some examples in the examples/ directory.
Who yo use it?
Write a rhythm. Compile it with "rc". Run the produced program. You are done.
See the examples/ directory to get the point.
When you run an example, try "-h" to get the available options.
It should be self-explanatory.
The rhythm compiler has several options. By running "rc --help", all should be clear.
Technical Details:
The compiler will parse the input file line by line.
If a line starts with "*" or "." (not counting leading white spaces), the whole line is seen as a rhythm line, and is transformed into C code. If not, it is passed as is to the C file.
Beware! You MUST NOT start any C code line by "*" or "."!
You can create as much functions as you want, write any C code you want. But remember that a line starting by "*" or "." is seen as a rhythm line and is translated by "rc" into C code.
You must provide a "void main_rhythm(void)" function, that will be called by the library. It is the starting point of your rhythm. It can be "void main_rhythm(int argc, char *argv[])" too, with common meaning for those parameters (non-C coders will have trouble with the Virtual Drum Machine).
You can change the tempo (ex. "tempo=100;") or the volume (ex "vol=0.4;") at any time. Each sample comes with its own volume and panning (ex. "a.vol = 0.1;" "a.pan=-0.8;"). Volumes range from 0 to what you want. 1 is for the normal volume. Panning ranges from -1 (left) to 1 (right). 0 is center. All values are double. You can use "volume" instead of "vol", and "panning" instead of "pan". There is no global panning, if you want all left, set all samples to left.
To run in stereo mode, dont forget "-s" when running the generated program. It is mono by default.
You absolutely need to compile and run the examples, and read them to get the point out of it!
The "rc.conf" file contains configuration informations. You specify the sample by "sample" followed by its name (the one you will use in your rhythm files), then the file that will be played. The name of the sample must start by a letter, followed by letters and/or numbers (it must be a valid C identifier, without "_" though). The configuration file contains the install directory, used by "rc" to compile your rhythms. Take a look at the one that is provided to see how to use it.
The sound files are simple wav files. They all should be of the same rate, which can be specified to the generated program, using the "-f" option (44100 is the default). (The library only handles very basic wav files, if yours dont work, you probably will have to modify the library for the program to handle it.)
When you add a sample, you must modify "rc.conf" for the changes to appear. The samples are hard-linked to the produced program, so if you change "sample a /some/dir/file1.wav" by "sample a /one/other/dir/file2.wav" in the configuration file, the previously generated programs will still use "/some/dir/file1.wav". You will have to compile them again to take the changes into account.
Enhancements:
- The code has been modified to let gcc 4 compile it.

The Linux Virtual Server is a highly scalable and highly available server built on a cluster of real servers, with the load balancer running on the Linux operating system.

The architecture of the server cluster is fully transparent to end users, and the users interact as if it were a single high-performance virtual server.

The basic goal of the Linux Virtual Server Project is to:
- Build a high-performance and highly available server for Linux using clustering technology, which provides good scalability, reliability and serviceability.

Virtual Console init is an /sbin/init clone for virtual consoles. It is very easy to set up and use because it has no configuration files.
It is very small and has builtin getty, login, klogd, and slogd. Virtual Console init is suitable for embedded systems and home Linux boxes.
This is a new kind of "init" that only works for the virtual console, so dont try it to login from a serial line. The idea is having a very simple init for home Linux systems (although it could work on other systems as well, who knows...), allowing for a simpler and cleaner configuration. It is useful too in embedded systems or tiny boot disks (maybe as a complement for "busybox"). In other words: it works for me, I use it and Im releasing it in the hope of it being useful for others.
The binary itself doesnt accept parameters, so lets go directly to the behaviour... It must be run by "root" and have PID 1, so dont try to run it yourself, it wont work... You should install it under "/sbin/init", and the kernel will run it automatically at boot.
Take into account that this "init" has both the "getty" and "login" parts built-in, not as separate binaries. This means that if you have a server or another binary which needs "/bin/login", it probably WONT WORK. The sysklog system (kernel logger and system logger, "klogd" and "slogd") are built-in, too. You dont need sysklogd or equivalent, unless you want some feature of them... In that case, you can disable the builtin system.
Enhancements:
- vcinit is now licensed under the GPLv2 only, and not necessarily any later version of the GPL.

virtualDesktopTools is a set of tools for handling X Window virtual desktops.

It makes it possible to switch the virtual desktop to the one indexed by a command line argument, and displays the number of desktops and index of the currently selected one.

It should work with all EWMH-compliant window managers.

Virtual Machine Manager software (virt-manager for short package name) is a desktop user interface for managing virtual machines. The project presents a summary view of running domains and their live performance & resource utilization statistics. A detailed view presents graphs showing performance & utilization over time. Ultimately it will allow creation of new domains, and configuration & adjustment of a domains resource allocation & virtual hardware. Finally an embedded VNC client viewer presents a full graphical console to the guest domain.

The application logic is written in Python, while the UI is constructed with Glade and GTK+, based on mockups provided by UI interaction designers. The libvirt Python bindings are used to interacting with the underlying hypervisor. This enables the application to be written independant of any particular hypervisor technology. Initially Xen was the primary platform supported, however, since libvirt 0.2.0 and virt-manager 0.3.1 it is possible to manage QEMU and KVM guests too. It is expected that support for additional hypervisors / virtualization products will expand even further over time as additional libvirt drivers are written.
The "Virt Install" tool (virtinst for short package name) is a command line tool which provides an easy way to provision operating systems into virtual machines. It also provides an API to the virt-manager application for its graphical VM creation wizard.

The "Virt Clone" tool (virtinst for short package name) is a command line tool for cloning existing inactive guests. It copies the disk images, and defines a config with new name, UUID and MAC address pointing to the copied disks.
The "Virtual Machine Viewer" application (virt-viewer for short package name) is a lightweight interface for interacting with the graphical display of virtualized guest OS. It uses GTK-VNC as its display capability, and libvirt to lookup the VNC server details associated with the guest. It is intended as a replacement for the traditional vncviewer client, since the latter does not support SSL/TLS encryption of x509 certificate authentication.