Книга: Embedded Linux development using Eclipse

Dstore Connection

The dstore protocol provides more capability than SSH at the expense of requiring a Java-based server running on the remote machine. dstore supports browsing into archive files such as tar, tgz, and zip. It supports remote search without transferring files to your local host. Nevertheless, the requirement for Java means it’s probably not the best fit for embedded devices.

Before creating a dstore connection, you must install the dstore server on the remote machine. Download it from the Target Management project download site at http://www.download.eclipse.org/dsdp/tm/downloads. Click on the latest release link, currently 3.0, and in that page scroll down to the DStore Server Runtime. Versions are available for Linux, Windows, other Unix, and Mac OS X (considered experimental). Currently, a server implementation for Windows CE is in “incubation.”

Decide where to install the server — on a Linux box /opt is a good place — and create a directory for it, say, /opt/rseserver. Untar the downloaded tar file there.

The dstore server also requires a Java Runtime Environment (JRE) version 1.4 or higher. An IBM, Sun, or equivalent JRE is required. The gcj-based jvm that comes with most Linux distributions doesn’t work. If necessary, refer back to Chapter 2, Installation, for information on installing a JRE. The scripts that start the Linux server also require Perl, which is installed by default on most distributions.

There are two ways to start the dstore server on a Linux remote system. As root user you can start a server daemon by executing the Perl script daemon.pl. The server daemon listens for connection requests on port 4075 by default. You can change the port number with an optional port argument to the script. In response to a connection request, the daemon spawns a dstore server.

Alternatively, if you don’t have root access, or just don’t want the daemon running, you can manually start the server with the Perl script server.pl. If you don’t specify a port, the server picks the first one available and prints out the port number. This is usually 4033. If no connection shows up in about two minutes, the server times out. A manually launched server also terminates when you terminate the connection.

The process is essentially the same for a Windows remote system, except that the scripts are called respectively daemon.bat and server.bat.

To establish a dstore connection, click the New Connection icon and select either Linux or Windows as the remote system type. Specify the host name and a connection name, just as we did for the SSH connection. Click Next. In this dialog (Figure 6.7) Launcher Properties specifies how the server is started on the remote system. If you started the daemon on the remote system, then select Daemon as the Launcher. If you manually started the server, select Running.

Click Finish. Right-click on the new entry in the Remote Systems view and click Connect.

Personally, I find the SSH Only connection to be simpler and easier to work with. Dstore is useful in connecting to Windows boxes, because standard Windows doesn’t include an SSH server.

Оглавление книги