From dff0b6243c3b214321a725ffdef5466e452d1b74 Mon Sep 17 00:00:00 2001 From: Martin Oberhuber < martin.oberhuber@windriver.com> Date: Fri, 30 Jun 2006 08:36:53 +0000 Subject: [PATCH] Update build notes and download page for M3 --- .../template/buildNotes.php | 63 ++++++++++++++----- .../org.eclipse.rse.build/template/index.php | 8 ++- 2 files changed, 53 insertions(+), 18 deletions(-) diff --git a/releng/org.eclipse.rse.build/template/buildNotes.php b/releng/org.eclipse.rse.build/template/buildNotes.php index 872dbca0f70..0dfb55ee3a5 100755 --- a/releng/org.eclipse.rse.build/template/buildNotes.php +++ b/releng/org.eclipse.rse.build/template/buildNotes.php @@ -26,13 +26,17 @@
  • RSE ssh feature now supports connections via Proxy.
    • -
  • Documentation is now available. Note that this documentation still refers to the - older IBM RSE product and thus contains lots of outdated references.
    • +
  • Documentation is now available. Note that this documentation partially still + refers to the older IBM RSE product and thus contains lots of outdated + references.
    • +
  • The New Connection Wizard is now completely replaceable for contributed + system types. As a side effect of this, the ordering of subsystems for a + connection may change (bug 149280).
  • Use this query to show the list of bugs fixed for this build.
  • Look @@ -79,8 +83,8 @@ For operations on an actual remote system, you can either

    RSE is a framework that supports plugging in many different communication protocols. -By default, the dstore and FTP protocol plug-ins are provided, with dstore being a -lot richer in features.

    +By default, the dstore, FTP and ssh protocol plug-ins are provided, with dstore being +the most richest in features.

    Dstore requirs a server to run on the remote system. There are several methods to get a server launched for a particular user, the most easy one to set up is the @@ -103,6 +107,24 @@ daemon method. To start a dstore launcher daemon, Note: In its default configuration for testing, the dstore daemon accepts unencrypted passwords from the RSE client. For production use, SSL can be enabled in order to encrypt connections, or the RSE server can be launched differently (e.g. through ssh).

    +

    +When no root access is available on the remote system (typically UNIX), normal +users can start a dstore server for themselves only, instead of a daemon: +

      +
    • On the remote system, run perl server.pl [portname]
      • +
    • On the RSE client, create the dstore connection
      • +
    • After creating the connection, select it and choose Properties +
      • On Server Launcher Settings, choose Connect to Running Server
        • +
      • On the Subsystem page, enter the port number you used for starting the server
        • +
      • +
    • When connecting, enter just anything for username and password (these will be ignored).
      • +
    • The server.pl script has more options, e.g. for using the first available + port instead of a well-known one, or for restricting access to a single + user ID. Since all dstore communication will be on the single TCP port, + this port can also be forwarded through an ssh tunnel if desired.
      • +
    + +
    @@ -116,12 +138,16 @@ connections, or the RSE server can be launched differently (e.g. through ssh).
  • In the RSE Perspective, Remote Systems View, press the New Connection button.
    • -
  • Enter a name, system type and IP address for a remote system running an ssh server or dstore server.
    • +
  • Select the desired system type
    • +
  • Enter an IP address for a remote system running an ssh server or dstore server. + A connection name will be suggested automatically, but can be changed.
  • Fill in the username / password dialog.
  • Browse remote files, or open remote shells.