9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Troy Cauble <troycauble@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] hg over ssh
Date: Thu, 15 Dec 2011 21:58:48 -0500	[thread overview]
Message-ID: <CAMhmq_9gk1XhDJYQV9_60TB3zVmk+CqW+V7FoODCGZ=huuE1UQ@mail.gmail.com> (raw)
In-Reply-To: <CAMhmq_9EjUwxxAw_oX4bkoFp8rNGhQXi_fC4PYn04dcJp7vtxA@mail.gmail.com>

> >  remote: abort: Bad file number
> >  abort: no suitable response from remote hg!

> for fun, run under ratrace and you'll see the problem. This may be the
> top of stack problem but I am not sure. I just don't recall.

Well execing /bin/sh problematic:

    730 hg Exec 230f1e 0x59fd40/"/bin/sh" 0x59fd60/"/bin/sh"
0x5a1b60/"-c" 0x5a19a0/"/bin/openssh/ssh -v -2 135.112.125.227 hg -R
foo2 serve --stdio" = 0xffffffff  1323985179203831089
1323985179204203215

I copied /bin/rc to /bin/sh and got the quoting problem I was looking
for before:
    remote: bash: hg -R foo2 serve --stdio: command not found

I could edit mercurial's sshrepo.py code to take out the quotes.
I could edit python's subprocess.py code to call rc instead of sh.
But maybe this has been solved before?
Maybe someone has a nice rc script for sh that would remove the quotes?

Also, I did have to generate keys, the ssh prompt doesn't get through to me.
Also, while it worked at least once (as far as the quote failure),
I seem to have to use '/bin/openssh/ssh -i /usr/troy/lib/ssh/ida_rsa' now.
It doesn't seem to look for ida_rsa there.

Ideas?

BTW, I'm using the stallion 1.7.5 contrib, not the bichued 1.0.2.

Thanks,
-troy



  parent reply	other threads:[~2011-12-16  2:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-15 21:44 Troy Cauble
2011-12-15 22:24 ` ron minnich
2011-12-16  2:58 ` Troy Cauble [this message]
     [not found] ` <CAMhmq_9gk1XhDJYQV9_60TB3zVmk+CqW+V7FoODCGZ=huuE1UQ@mail.gmail.c>
2011-12-16  3:16   ` erik quanstrom
2011-12-16  4:10     ` Troy Cauble
2011-12-16  7:31       ` Federico Benavento

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAMhmq_9gk1XhDJYQV9_60TB3zVmk+CqW+V7FoODCGZ=huuE1UQ@mail.gmail.com' \
    --to=troycauble@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).