Re: [Gnu-arch-users] MSFU and tla with openssh vs. plink

[John Arbash Meinel]

Deliverable Mail wrote:

> I've tried all the patched versions of tla under cygwin, and none
> interoperated with linux.  Tails of the paths seem corrupted back on
> linux.
As a maintainer of one of the cygwin ports, I would like to know what
you tried.
From this page:
http://wiki.gnuarch.org/Native_20WIN32_20Support

I have had success with my port
(http://ct.radiology.uiowa.edu/~jfmeinel/tla-short-path). Though some
others have had some problems. It's also not perfect if names get big
enough, but it works for general use.

For: Lode Leroy's cygwin version here:
http://www.geocities.com/lode_leroy/arch/
I never got the dos83 versions to work, but I had good luck with the
dirnames versions. The 1.2.1 versions had a problem with line endings
and he doesn't seem to distribute the 1.2 versions (he might have fixed
the line ending, it turns out you need to give diff & patch the
'--binary' flag to make them work correctly.)

I have a 1.2 version on my machine that I can post somewhere if you want it.

I have never had success with Johannes Port, as the ssh he bundled
always seemed to hang for me.

I also have never tried MSFU, though I have heard of it.

> So I went the MSFU (M$ Services For Unix) way, which turns out to be a
> thing similar to cygwin, with packages at www.interix.com.  Following
> the instructions at wiki.gnuarch.org, I did get a working tla.  The
> issue, however, is to get it to fetch and propagate archives.  So we
> need ssh.
>
> The ssh which can be loaded into MSFU via pkg_add is openssh, and its
> ssh-agent can be started, but ssh-add cannot talk to it, saying broken
> pipe on the socket.  So following teh approach of those using darcs
> with pscp, I replaced sftp with pusftp and pageant.
>
> Then I saw that tla wants to push openssh options -oForwardX11=no and
> two more -o's down plink's throat.  The source shows that the ssh
> choice is a compile-time one, with the options hardcoded!  Wonderful.
> I've recompiled it for plink and have a separate copy tla-plink, but I
> believe it would be nice to decouple the transport choice and have a
> way to specify options through to it, much like gcc does with ld.
I agree, I though there was a compile option for this. But you need to use:
../configure --help-options
In order to see what the real options are.
Specifically it had the options for
ssh, ssh-is-openssh, and ssh-is-lsh

You might try using:
../configure --with-ssh-is-openssh=no --with-ssh=/path/to/plink

I would agree that an extra configure option for
--with-ssh-options='...' would be nice.

> Anyone tried UWIN?  What's the wisdom about Cygwin vs. MSFU vs. UWIN
> these days?  At least MSFU supports tla naturally...
Well, I've been using a cygwin version for quite some time. I'm not
really sure what you mean by "naturally" or what specific problems
you've been having. I *am* glad to see that you got it working under a
different setup.
I use cygwin because I use it for other things, so it is natural to keep
using it for me. It certainly would be nice to see a more native tla
binary, and I think Johannes Port is a good way towards that.

But I don't think his code gets exercised regularly by many people. I
also believe he is on vacation until the 19th, so he probably won't
respond for a while.

> Cheers,
> Alexy
John
=:->

signature.asc
Description: OpenPGP digital signature