From: Alexander Aring <alex.aring@gmail.com>
To: ptxdist@pengutronix.de
Cc: Oliver Graute <oliver.graute@neuhaus.de>
Subject: Re: [ptxdist] [PATCH] added mosh package to ptxdist
Date: Tue, 10 Feb 2015 09:02:39 +0100 [thread overview]
Message-ID: <20150210080238.GA21110@omega> (raw)
In-Reply-To: <20150210075318.GA19979@omega>
Hi,
I missed something, please add also a name before your mail subject
like:
[PATCH] mosh: added mosh package to ptxdist
On Tue, Feb 10, 2015 at 08:53:18AM +0100, Alexander Aring wrote:
> Hi,
>
> I have also some rules for mosh, but I added IPv6 support on it (which
> is available on the github master branch).
> Nevertheless I have some issues with mosh and IPv6 and that was the
> reason why I didn't send it mainline. I try to compare now my rule with
> your rule.
>
> On Tue, Feb 10, 2015 at 08:05:21AM +0100, Oliver Graute wrote:
> > added a rule for mosh
> >
> > Signed-off-by: Oliver Graute <oliver.graute@neuhaus.de>
> > ---
> > rules/mosh.in | 7 ++++
> > rules/mosh.make | 102 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > 2 files changed, 109 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..1866a4d
> > --- /dev/null
> > +++ b/rules/mosh.in
> > @@ -0,0 +1,7 @@
> > +## SECTION=networking
> > +
> > +config MOSH
> > + tristate
> > + prompt "mosh"
>
> In my rule file I have:
>
> select PROTOBUF
> select NCURSES
> select ZLIB
> select OPENSSL
>
> Additional I detected (because installing the mosh perl script):
>
> select PERL
> select IO_SOCKET_IP_PERL
this should all if RUNTIME, because it's only necessary if you running
the mosh script at runtime.
If you don't want to install the mosh script, maybe we could add a own
config there. Something like "config MOSH_INSTALL_MOSH_SCRIPT".
> select OPENSSH if RUNTIME
> select OPENSSH_SSH if RUNTIME
> select OPENSSH_SSHD if RUNTIME
>
.....
> > +#MOSH_CONF_OPT := $(CROSS_AUTOCONF_USR)
> > +
>
> #
> # autoconf
> #
> MOSH_AUTOCONF := \
> $(CROSS_AUTOCONF_USR) \
> --enable-hardening \
> --enable-client \
> --enable-server \
> --disable-examples \
> --enable-ufw \
the ufw is some ubuntu firewall helper thingy. Better to disable it
here. We don't have such fancy stuff. :-)
- Alex
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2015-02-10 8:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 7:05 Oliver Graute
2015-02-10 7:53 ` Alexander Aring
2015-02-10 8:02 ` Alexander Aring [this message]
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
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=20150210080238.GA21110@omega \
--to=alex.aring@gmail.com \
--cc=oliver.graute@neuhaus.de \
--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