mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
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 11:55:51 +0100	[thread overview]
Message-ID: <20150216105548.GD8708@omega> (raw)
In-Reply-To: <20150216103840.GA30223@pengutronix.de>

On Mon, Feb 16, 2015 at 11:38:40AM +0100, Michael Olbrich wrote:
> On Mon, Feb 16, 2015 at 10:52:01AM +0100, Alexander Aring wrote:
> > On Mon, Feb 16, 2015 at 10:39:34AM +0100, Michael Olbrich wrote:
> > > On Tue, Feb 10, 2015 at 09:44:37AM +0100, Oliver Graute wrote:
> > > > second try, thank you for feedback its my first contribution to ptxdist  
> > > 
> > > Thanks, I've applied it with some cleanups: Make sure you handle the
> > > white-spaces correctly in future patches. And Alex got it wrong. It should
> > > be:
> > > 
> > > MOSH_CONF_TOOL	:= autoconf
> > > MOSH_CONF_OPT	:= \
> > > [...]
> > > 
> > > Michael
> > > 
> > > 
> > > > Signed-off-by: Oliver Graute <oliver.graute@neuhaus.de>
> > > > ---
> > > >  rules/mosh.in   |   17 ++++++++++++++++
> > > >  rules/mosh.make |   61 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > > >  2 files changed, 78 insertions(+)
> > > >  create mode 100644 rules/mosh.in
> > > >  create mode 100644 rules/mosh.make
> > > > 
> > > > diff --git a/rules/mosh.in b/rules/mosh.in
> > > > new file mode 100644
> > > > index 0000000..d9cc583
> > > > --- /dev/null
> > > > +++ b/rules/mosh.in
> > > > @@ -0,0 +1,17 @@
> > > > +## SECTION=networking
> > > > +
> > > > +config MOSH
> > > > +	tristate
> > > > +	prompt "mosh"
> > > > +select PROTOBUF
> > > > +         select NCURSES
> > > > +         select ZLIB
> > > > +         select OPENSSL
> > > > +         select OPENSSH                      if RUNTIME
> > > > +         select OPENSSH_SSH              if RUNTIME
> > > > +         select OPENSSH_SSHD                 if RUNTIME
> > 
> > now I see, there is PERL missing here.
> > 
> > The mosh script require PERL with:
> > 
> > select PERL if RUNTIME
> > 
> > also the mosh script uses:
> > 
> > use IO::Socket::INET;, see [0].
> > 
> > that means we need also a:
> > 
> > select IO_SOCKET_INET6_PERL if RUNTIME, see [1].
> > 
> > [0] https://github.com/keithw/mosh/blob/mosh-1.2.4/scripts/mosh#L153
> > [1] http://search.cpan.org/~shlomif/IO-Socket-INET6-2.72/lib/IO/Socket/INET6.pm
> 
> Is it usefull without perl? Maybe the server could be startet without it?
> The we should add an option for this.
> 

yep, option would be great.

For myself I don't know how to create a mosh connection without the mosh
script (this is only possible if you do some own hard work). On
website stands:

---

The mosh command is a wrapper script that is designed to be the primary way
that you use mosh. In most cases, you can simply just replace "ssh" with
"mosh" in your command line. Behind the scenes, the mosh wrapper script
will SSH to the server, start up mosh-server, and then close the SSH
connection. Then it will start up the mosh-client executable on the client,
passing it the necessary information for it to connect to the newly spawned
mosh-server instance.

In normal usage, mosh-client and mosh-server don't need to be run directly.

---

Afterwards there is a complicated How-To how you setup a connection
without mosh script. See [0], "Q: How do I run the mosh client and
server separately?".

I am fine to add a option and we have already a perfect help message see
above.

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"'.


btw: another issue is maybe the OPENSSH_SSH and OPENSSH_SSHD, if you
want only be a server or a client. This "could" be an option which
select OPENSSH_SSH or OPENSSH_SSHD when client or server only, but I
would keep it in this way. Otherwise it would be much complicated to
deal with the dependencies.

- Alex

[0] https://mosh.mit.edu/
[1] http://article.gmane.org/gmane.comp.embedded.ptxdist.devel/12592

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2015-02-16 10:56 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 [this message]
2015-02-16 11:02           ` Michael Olbrich
2015-02-16 11:04           ` Alexander Aring

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=20150216105548.GD8708@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