Hi all,
I am using native Plan9.
I tried to create a remote Mercurial repository via 'ssh':
term% hg init ssh://xxx.yyy.zzz/test --verbose
running ssh xxx.yyy.zzz "hg init test"
running ssh xxx.yyy.zzz "hg -R test serve --stdio"
remote: abort: Bad file number
abort: no suitable response from rem
On Sat, May 31, 2014 at 7:41 AM, Pavel Klinkovský
wrote:
> Hi all,
>
> I am using native Plan9.
Hi Pavel,
Internally, Mercurial makes calls to OpenSSH, which doesn't quite work
as advertised on Plan 9. For the most part, using HTTP/S repositories
will give you the best bang for the proverbial bu
Hi Steven,
For the most part, using HTTP/S repositories will give you the best bang
> for the proverbial buck.
I see. In fact I tried to create and use Mercurial repository via 'ssh' and
'ftp' (via ftpfs) and none of them works.
Pavel
On May 31, 2014, at 8:43 AM, Pavel Klinkovský
wrote:
> Hi Steven,
>
> For the most part, using HTTP/S repositories will give you the best bang for
> the proverbial buck.
>
> I see. In fact I tried to create and use Mercurial repository via 'ssh' and
> 'ftp' (via ftpfs) and none of them work
> I’ve never been able to get the ssh v2 version to work on Plan 9 for testing.
Never had any major problem[1] with ssh2 (using the one from labs, with
factotum, not nfactotum).
[1] a small problem is that I needed to patch srvssh like this:
http://okturing.com/src/2230/body
--
Aram Hăvărneanu
On May 31, 2014, at 11:03 AM, Aram Hăvărneanu wrote:
>> I’ve never been able to get the ssh v2 version to work on Plan 9 for testing.
>
> Never had any major problem[1] with ssh2 (using the one from labs, with
> factotum, not nfactotum).
Are you running it on your auth server? I’m not, don’t
I'm using it only as a client. I don't see the point in using it in
other capacity on Plan 9.
--
Aram Hăvărneanu
On Sat May 31 09:44:35 EDT 2014, pavel.klinkov...@gmail.com wrote:
> Hi Steven,
>
> For the most part, using HTTP/S repositories will give you the best bang
> > for the proverbial buck.
>
>
> I see. In fact I tried to create and use Mercurial repository via 'ssh' and
> 'ftp' (via ftpfs) and non
On May 31, 2014, at 11:20 AM, Aram Hăvărneanu wrote:
> I'm using it only as a client. I don't see the point in using it in
> other capacity on Plan 9.
I too have tried to use it as a client, with zero success. Thus
no testing for hg ssh://.
-jas
> I too have tried to use it as a client, with zero success. Thus
> no testing for hg ssh://.
Well what's the problem? "Doesn't work" is not a valid bug report.
cpu% grep ssh /mnt/factotum/ctl
key proto=rsa service=ssh size=1024 ek=2F
n=F856C9BC1E9B881A0CB2DE4CA642A752586010DED7ED729EDEBA54303D4
> I didn't do anything more special except adding keys to factotum.
one problem with ssh2 is the fact that it doesn't do keyboard interactive
at all, and doesn't give an error message that makes that apparent.
i've used the client successfully, especially to dell and arista switches.
- erik
On May 31, 2014, at 12:07 PM, Aram Hăvărneanu wrote:
> I didn't do anything more special except adding keys to factotum.
Did you add the key to factotum _before_ using ssh2 to connect?
I’ve always tried to get factotum to do what it’s suppose to do,
store the key _after_ using ssh2 to connect t
On Sat, May 31, 2014 at 8:12 PM, Jeff Sickel wrote:
> Did you add the key to factotum _before_ using ssh2 to connect?
> I’ve always tried to get factotum to do what it’s suppose to do,
> store the key _after_ using ssh2 to connect to a remote host.
Of course you need to add the key before using s
On May 31, 2014, at 1:26 PM, Aram Hăvărneanu wrote:
> I use secstore to hold my key.
Ah, but I use ssh w/o authorized_keys. So no, I don’t populate
a key store with a public key. Just tike `cpu -h somehost` for
the first time, I anticipate that I’ll get a prompt that will only
store a key in
ssh2 doesn't work with passwords (at least not without changing server
settings), you need to use keys.
--
Aram Hăvărneanu
> ssh2 doesn't work with passwords (at
> least not without changing server
> settings), you need to use keys.
It does work with real password auth, but current OpenSSH
distros default to not allowing real password auth. They use
keyboard-interactive instead, and it's set up to look to the
user ju
It seems I do not fully understand the discussion about ssh...
When I manually make this command (what 'hg' does)...
ssh xxx.yyy.zzz "hg init test"
...the result is:
bash: hg: Command not found...
When I manually modify it...
ssh xxx.yyy.zzz 'hg init test'
...the result is...
!Adding key
FWIW I use ssh2 daily to connect to linux machines,
command line and using sftpfs to get file access.
> one problem with ssh2 is the fact that it doesn't do keyboard interactive at
> all
One more - sshnet is not yet ported to ssh2, though this is on my list of
things to do.
-Steve
> When I manually make this command (what 'hg' does)...
>
> ssh xxx.yyy.zzz "hg init test"
>
>
> ...the result is:
>
> bash: hg: Command not found...
>
>
> When I manually modify it...
>
>
> ssh xxx.yyy.zzz 'hg init test'
>
> ...the result is...
>
> !Adding key: proto=pass server=xxx.yyy.
On Sat May 31 12:55:25 EDT 2014, ara...@mgk.ro wrote:
> > I’ve never been able to get the ssh v2 version to work on Plan 9 for
> > testing.
>
> Never had any major problem[1] with ssh2 (using the one from labs, with
> factotum, not nfactotum).
the version of factotum is a red herring, as the fac
20 matches
Mail list logo
