From: Alexander Aring <alex.aring@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCHv2] mosh: added mosh package to ptxdist
Date: Mon, 16 Feb 2015 12:04:00 +0100 [thread overview]
Message-ID: <20150216110359.GE8708@omega> (raw)
In-Reply-To: <20150216105548.GD8708@omega>
On Mon, Feb 16, 2015 at 11:55:48AM +0100, Alexander Aring wrote:
...
>
> I also mentioned to add a config for the mosh script in some of my
> previous mail. [1] 'Something like "config MOSH_INSTALL_MOSH_SCRIPT"'.
>
There is a mistake in my previous mail it's IO_SOCKET_INET6_PERL not
IO_SOCKET_IP_PERL. They changed it for IPv6 functionality which I
tried to get working. This rule is also not mainline, it's inside my
private working BSP. Sorry! :-)
btw:
For the issue with IPv6 support, I think I have some missing dependency
which I don't know. It works on client (ptxdist) and server (arch-linux)
doesn't depend if 6LoWPAN connection or Ethernet IPv6.
The server simple doesn't work on ptxdist and I had no time now to debug
the issue. I also need to hard set "LANG=en_US.UTF-8" before running
mosh otherwise the application will not start. But this is a common
issue and all other people get it working by setting "LANG=en_US.UTF-8".
I need to look into that how ptxdist can deal with that.
- Alex
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2015-02-16 11:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 7:05 [ptxdist] [PATCH] " Oliver Graute
2015-02-10 7:53 ` Alexander Aring
2015-02-10 8:02 ` Alexander Aring
2015-02-10 7:59 ` Marc Kleine-Budde
2015-02-10 8:44 ` [ptxdist] [PATCHv2] mosh: " Oliver Graute
2015-02-16 9:39 ` Michael Olbrich
2015-02-16 9:42 ` Alexander Aring
2015-02-16 9:52 ` Alexander Aring
2015-02-16 10:38 ` Michael Olbrich
2015-02-16 10:55 ` Alexander Aring
2015-02-16 11:02 ` Michael Olbrich
2015-02-16 11:04 ` Alexander Aring [this message]
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=20150216110359.GE8708@omega \
--to=alex.aring@gmail.com \
--cc=ptxdist@pengutronix.de \
/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