From: Quentin Smith <quentin@MIT.EDU>
To: Dave Taht <dave.taht@gmail.com>
Cc: mosh-devel@mit.edu, Alex Chernyakhovsky <achernya@mit.edu>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [mosh-devel] mosh-server vs dropbear vs openwrt
Date: Mon, 21 Oct 2013 17:53:34 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1310211752300.14869@team-rocket.mit.edu> (raw)
In-Reply-To: <CAA93jw5g8rrzun8Vw3gUD9tbUU58zQKzXJ3=SHmBDk82s6WjqQ@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 2238 bytes --]
Are you able to run mosh-server by hand and connect to it? ("How do I run
the mosh client and server separately?" on the FAQ, if you don't know how
to do that.) These look like errors from dropbear.
--Quentin
On Mon, 21 Oct 2013, Dave Taht wrote:
> On Mon, Oct 21, 2013 at 2:27 PM, Alex Chernyakhovsky <achernya@mit.edu> wrote:
>> Do you have devpts mounted on /dev/pts?
>>
>> Sincerely,
>> -Alex
>>
>>
>> On Mon, Oct 21, 2013 at 5:21 PM, Dave Taht <dave.taht@gmail.com> wrote:
>>> I have a basically compiling mosh-server for openwrt in my
>>> ceropackages-3.3 repository for a while now,
>>> pulling from commit 45bba44c83d0b5f6da32327bbcbd2a42d22adbb2 for mosh.
>>>
>>> I'm still getting this error, and I'm puzzled as to what to point fingers at.
>>>
>>> Mon Oct 21 21:18:04 2013 authpriv.err dropbear[2995]:
>>> ioctl(TIOCSCTTY): Input/output error
>>> Mon Oct 21 21:18:04 2013 authpriv.err dropbear[2995]: /dev/pts/1: No
>>> such file or directory
>>> Mon Oct 21 21:18:04 2013 authpriv.err dropbear[2995]: open /dev/tty
>>> failed - could not set controlling tty: No such device or address
>>> Mon Oct 21 21:18:05 2013 authpriv.info dropbear[2994]: Exit (root):
>>> Disconnect received
>>>
>>>
>>> --
>>> Dave Täht
>>>
>>> Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
>>>
>>> _______________________________________________
>>> mosh-devel mailing list
>>> mosh-devel@mit.edu
>>> http://mailman.mit.edu/mailman/listinfo/mosh-devel
>
> yes:
>
> root@cerowrt:~# mount
> /dev/root on /rom type squashfs (ro,relatime)
> proc on /proc type proc (rw,noatime)
> sysfs on /sys type sysfs (rw,noatime)
> tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime)
> /dev/mtdblock5 on /overlay type jffs2 (rw,noatime)
> overlayfs:/overlay on / type overlayfs (rw,noatime,lowerdir=/,upperdir=/overlay)
> tmpfs on /dev type tmpfs (rw,relatime,size=512k,mode=755)
> devpts on /dev/pts type devpts (rw,relatime,mode=600)
> debugfs on /sys/kernel/debug type debugfs (rw,noatime)
>
>
> --
> Dave Täht
>
> _______________________________________________
> mosh-devel mailing list
> mosh-devel@mit.edu
> http://mailman.mit.edu/mailman/listinfo/mosh-devel
>
next prev parent reply other threads:[~2013-10-21 21:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 21:21 [Cerowrt-devel] " Dave Taht
2013-10-21 21:27 ` [Cerowrt-devel] [mosh-devel] " Alex Chernyakhovsky
2013-10-21 21:30 ` Dave Taht
2013-10-21 21:53 ` Quentin Smith [this message]
2013-10-21 22:16 ` Dave Taht
2013-10-21 22:55 ` Outback Dingo
2013-10-21 23:03 ` Quentin Smith
2013-10-22 3:02 ` Anders Kaseorg
2013-10-22 3:06 ` Dave Taht
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1310211752300.14869@team-rocket.mit.edu \
--to=quentin@mit.edu \
--cc=achernya@mit.edu \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=mosh-devel@mit.edu \
/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