-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OK then...
Because it would break an officially supported use case (rsh). It would
also break the lsh utility included with rsync (in the support dir).
The --rsh parameter is for specifying alternative remote shells that are
command line compatible w
On 10/20/2011 12:08 AM, Kevin Korb wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I should also point out that I am not making up cool distinctive names
for my config file. I am using that actual host name of the system that
I am trying to connect to so that I can type 'ssh hostname' as i
On 10/19/2011 11:38 PM, Cameron Simpson wrote:
On 19Oct2011 22:14, Brian K. White wrote:
| On 10/19/2011 6:58 PM, Cameron Simpson wrote:
|>On 19Oct2011 12:02, Benjamin R. Haskell wrote:
|>| rsync has to parse the URL you're passing. The fact that it then
|>| takes that and runs something like
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I should also point out that I am not making up cool distinctive names
for my config file. I am using that actual host name of the system that
I am trying to connect to so that I can type 'ssh hostname' as if I were
plugged into the LAN that it was on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/19/11 18:58, Cameron Simpson wrote:
> On 19Oct2011 12:02, Benjamin R. Haskell wrote:
> | On Wed, 19 Oct 2011, Kevin Korb wrote:
> | >Because it is an even bigger joy to be able to type 'ssh newhost'
> | >and have it just work even though you can
On Thu, 20 Oct 2011, Cameron Simpson wrote:
On 19Oct2011 12:02, Benjamin R. Haskell wrote:
| On Wed, 19 Oct 2011, Kevin Korb wrote:
| >Because it is an even bigger joy to be able to type 'ssh newhost'
| >and have it just work even though you can't talk to newhost. You
| >can do that by properl
On 19Oct2011 22:14, Brian K. White wrote:
| On 10/19/2011 6:58 PM, Cameron Simpson wrote:
| >On 19Oct2011 12:02, Benjamin R. Haskell wrote:
| >| rsync has to parse the URL you're passing. The fact that it then
| >| takes that and runs something like `$RSYNC_RSH -l user host` is
| >| because rsyn
On 10/19/2011 6:58 PM, Cameron Simpson wrote:
On 19Oct2011 12:02, Benjamin R. Haskell wrote:
| On Wed, 19 Oct 2011, Kevin Korb wrote:
|>Because it is an even bigger joy to be able to type 'ssh newhost'
|>and have it just work even though you can't talk to newhost. You
|>can do that by properly
On 19Oct2011 12:02, Benjamin R. Haskell wrote:
| On Wed, 19 Oct 2011, Kevin Korb wrote:
| >Because it is an even bigger joy to be able to type 'ssh newhost'
| >and have it just work even though you can't talk to newhost. You
| >can do that by properly configuring ssh in ~/.ssh/config with
| >some
On Wed, 19 Oct 2011, Kevin Korb wrote:
Because it is an even bigger joy to be able to type 'ssh newhost' and
have it just work even though you can't talk to newhost. You can do
that by properly configuring ssh in ~/.ssh/config with something like
this:
Host accessiblehost
User cameron
Hos
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Because it is an even bigger joy to be able to type 'ssh newhost' and
have it just work even though you can't talk to newhost. You can do
that by properly configuring ssh in ~/.ssh/config with something like this:
Host accessiblehost
User cameron
Why does rsync believe it knows more about the use of the token to the left
of the colon than the program which will be used as the remote connection?
I have a script called sshto with accepts targets like this:
host1!host2!host3
and constructs the requisite ssh ProxyCommand options to do a mu
12 matches
Mail list logo