The intention for this project is a very simple API to call different kinds of services (provider/technology). Crispy's aims is to provide a single point of entry for remote invocation for a wide number of transports: eg. RMI, EJB, JAX-RPC or XML-RPC. It works by using properties to configure a service manager, which is then used to invoke the remote API. Crispy is a simple Java codebase with an API that sits between your client code and the services your code must access. It provides a layer of abstraction to decouple client code from access to a service, as well as its location and underlying implementation. The special on this idea is, that these calls are simple Java object calls (remote or local calls are transparent).
rsvndump is a command line tool that is able to dump a Subversion repository that resides on a remote server. All data is dumped in the format that can be read an written by svnadmin dump, so the data which is produced can easily be importerd into a new Subversion repository.
Actually, a remote dump can be done using svnsync and svnadmin dump on the locally synced repository. However, if the remote server does not run Subversion 1.5 or later, svnsync is unable to dump subdirectories of a repository only. This can be solved by syncing the whole repository and using svndumpfilter afterwards, but data of other subdirectories needs to be transferred over the network for no reason. And if you don't have access to the repository root, the whole thing will not work.
Long story short: If you want to dump a subdirectory of a remote repository which runs a version of Subversion prior to 1.5, this is the right tool for you. If not, please consider using svnsync.
rsvndump is written in C and built on top of the Subversion API, so it can offer all functionality needed to access a Subversion repository, including SSL authentication. And it's GPLed.
Wake-on-LAN (or WOL), which—as the name suggests—turns on your PC through your local network. Wake-on-LAN is a breeze to set up and use on your local network, and with a little legwork you can set it up so you can wake your computer away from your hom
Opticks is an expandable remote sensing and imagery analysis software platform that is free and open source. If you've used other commercial tools like: ERDAS IMAGINE, RemoteView, ENVI, or SOCET GXP, then you need to give Opticks a try. Unlike other competing tools, you can add capability to Opticks by creating an extension. Opticks provides the most advanced extension capability of any other remote sensing tool on the market.
mRemoteNG is a fork of mRemote, an open source, tabbed, multi-protocol, remote connections manager. mRemoteNG adds bug fixes and new features to mRemote. It allows you to view all of your remote connections in a simple yet powerful tabbed interface. mRemoteNG supports the following protocols: * RDP (Remote Desktop/Terminal Server) * VNC (Virtual Network Computing) * ICA (Citrix Independent Computing Architecture) * SSH (Secure Shell) * Telnet (TELecommunication NETwork) * HTTP/HTTPS (Hypertext Transfer Protocol) * rlogin * Raw Socket Connections mRemoteNG is now available. Download it now!
To connect to a virtual machine with a VNC client, you must modify the virtual machine's configuration file (.vmx) while the virtual machine is powered off.
Open the file in a text editor and add the following lines:
RemoteDisplay.vnc.enabled = TRUE
Setting this option to TRUE enables standard VNC support. This setting is valid only while the virtual machine is running. If the virtual machine is powered off, you cannot connect to it with a VNC client.
RemoteDisplay.vnc.port =
Specify the port the VNC client uses to connect to the virtual machine. 5900 is the default VNC port used for . If you want to connect to more than one virtual machine on the same host with a VNC client, you must specify a unique port number for each virtual machine. VMware suggests you use a port number in the range from 5900 to 5999. You can use any port number, but keep in mind that certain port numbers are used by other applications while others are privileged (meaning only the root or Administrator user can listen). For example, the VMware Management Interface uses ports 8333 and 8222; on Linux, only root can listen to ports up to port number 1024. Conflicts can occur if you specify a port in use by another application.
If you add RemoteDisplay.vnc.enabled = TRUE to your configuration file without specifying the port number option, the virtual machine uses port 5900, the default VNC port number. Note that only one virtual machine can use a given port number at a time.
RemoteDisplay.vnc.password =
GSX Server 3 supports VNC 3.3 authentication, which is an eight character password. Use this password when you are prompted for authentication as you use the VNC client to connect to the virtual machine.
M. Andreasen, H. Nielsen, S. Schrøder, и J. Stage. CHI '07: Proceedings of the SIGCHI conference on Human factors in computing systems, стр. 1405--1414. New York, NY, USA, ACM, (2007)