From: "Clay D. Montgomery" <clay@montgomery1.com>
To: yocto@yoctoproject.org
Subject: Re: Sftp deploy hangs when using dropbear and yocto fido.
Date: Sat, 25 Jul 2015 10:30:19 -0500 [thread overview]
Message-ID: <55B3AB8B.2060303@montgomery1.com> (raw)
In-Reply-To: <loom.20150724T210947-218@post.gmane.org>
On 7/24/2015 2:20 PM, Adam Sherman wrote:
> Måns Andersson <Mans.Andersson@...> writes:
>
>> Does anyone know about a problem with dropbear and openssh-sftp-server on
> Yocto Fido?
>> After upgrading my build from Dora to Fido the deployment of builds from
> QtCreator (3.2.2) to my qemuarm
>> build stopped working. It just hangs waiting as if it's working, i.e. no
> error message. I've switched
>> toolchains and emulator images from my Dora and Fido builds back and forth
> and the only common denominator
>> when it doesn't work is when using the Fido qemuarm build. Regular SSH
> connections and manual sftp
>> transfers (i.e. not initiated by Qt Creator) works, which just makes it
> even harder to debug.
>> Thanks in advance.
>> // Måns
>>
> Just to let you know, I have the same behavior with QtCreator (3.4.2) /
> trying to deploy on the Armadeus APF27 embedded Linux Arm Platform
> (Buildroot 2015.02 / Dropbear / openssh sftp server).
>
> Similarly, stand-alone sftp transfers outside of QtCreator work just fine.
>
> Adam Sherman
I am curious why continue to use dropbear anyway?
The openssh-sftp-server will likely work better with openssh than
with dropbear.
Openssh uses only about 3MB more per session than dropbear, which is
small unless you need a lot of simultaneous sessions.
I think dropbear is a relic from when systems had less RAM. Just
curious. Maybe I'm missing something.
Regards, Clay Montgomery
prev parent reply other threads:[~2015-07-25 15:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 14:07 Sftp deploy hangs when using dropbear and yocto fido Måns Andersson
2015-07-24 19:20 ` Adam Sherman
2015-07-25 0:27 ` Khem Raj
2015-07-25 14:42 ` Adam Sherman
2015-07-25 15:30 ` Clay D. Montgomery [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=55B3AB8B.2060303@montgomery1.com \
--to=clay@montgomery1.com \
--cc=yocto@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.