From mboxrd@z Thu Jan  1 00:00:00 1970
From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] sam and ssh
Message-ID: <20020327214719.H25951@cackle.proxima.alt.za>
References: <20020327182954.5796B1998C@mail.cse.psu.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <20020327182954.5796B1998C@mail.cse.psu.edu>; from Geoff Collyer on Wed, Mar 27, 2002 at 10:29:46AM -0800
Date: Wed, 27 Mar 2002 21:47:19 +0200
Topicbox-Message-UUID: 6e471440-eaca-11e9-9e20-41e7f4b1d025

On Wed, Mar 27, 2002 at 10:29:46AM -0800, Geoff Collyer wrote:
> 
> I think you have to compile; find "rsh" in the [Mm]*k*files and change
> it to "ssh".  sam will then run another sam on the remote system via
> ssh when you type "sam -r remote-system".  You have to arrange things
> so that the remote side has your public ssh key and you don't have a
> passphrase protecting your ssh keys.

If I'm going to recompile sam, I may as well make that a command line
option, although I think Scott's suggestion of mounting ssh in rx's
place is excellent.

"s" is already taken as a sam command line option, it is tempting to
use a capital "R" instead of the lower case, but I think that may be
counter-intuitive in some fashion.

As for identity, I'm prepared to use ~/.shost (multiple heresy!) at
least initially, and Russ's "agent" may be what I need, although I
have trouble understanding that.

Further opinions/suggestions?

++L