From: Outback Dingo <outbackdingo@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] mosh makes it in...
Date: Sun, 9 Feb 2014 17:14:30 -0500 [thread overview]
Message-ID: <CAKYr3zz+3CAqyihm-tmMc7LK7wMYxCkFOb9OfOxYCd-Z5MdHuA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5kSAitkPSKEsJWcxN-aNTm0nM02Ym8v4G_PJMw8QLGcw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2224 bytes --]
Wow, cool... be my guest.........
On Sun, Feb 9, 2014 at 5:13 PM, Dave Taht <dave.taht@gmail.com> wrote:
> What is so hard about fixing dropbear?
>
> On Sun, Feb 9, 2014 at 2:08 PM, Outback Dingo <outbackdingo@gmail.com>
> wrote:
> > mosh currently depends on openssh-client.
> >
> >
> > On Sun, Feb 9, 2014 at 3:24 PM, Dave Taht <dave.taht@gmail.com> wrote:
> >>
> >> Grump. Build still has same error it's always had.
> >>
> >> Sun Feb 9 20:23:41 2014 authpriv.err dropbear[27166]:
> >> ioctl(TIOCSCTTY): Input/output error
> >> Sun Feb 9 20:23:41 2014 authpriv.err dropbear[27166]: /dev/pts/2: No
> >> such file or directory
> >> Sun Feb 9 20:23:41 2014 authpriv.err dropbear[27166]: open /dev/tty
> >> failed - could not set controlling tty: No such device or address
> >> Sun Feb 9 20:23:42 2014 authpriv.info dropbear[27165]: Exit (root):
> >> Disconnect received
> >>
> >> On Sun, Feb 9, 2014 at 2:59 AM, Outback Dingo <outbackdingo@gmail.com>
> >> wrote:
> >> > damn....... my bad working at 4AM with no caffiene..... scripts/feeds
> >> > install mosh-server ............ not mosh
> >> >
> >> >
> >> > On Sun, Feb 9, 2014 at 12:16 AM, Outback Dingo <
> outbackdingo@gmail.com>
> >> > wrote:
> >> >>
> >> >> However it is not showing up in make menuconfig, and a search
> displays
> >> >> no
> >> >> results in menuconfig
> >> >>
> >> >>
> >> >> On Sat, Feb 8, 2014 at 11:35 PM, Dave Taht <dave.taht@gmail.com>
> wrote:
> >> >>>
> >> >>> https://dev.openwrt.org/changeset/39541
> >> >>>
> >> >>> made my day.
> >> >>>
> >> >>> --
> >> >>> Dave Täht
> >> >>>
> >> >>> Fixing bufferbloat with cerowrt:
> >> >>> http://www.teklibre.com/cerowrt/subscribe.html
> >> >>> _______________________________________________
> >> >>> Cerowrt-devel mailing list
> >> >>> Cerowrt-devel@lists.bufferbloat.net
> >> >>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
> >> >>
> >> >>
> >> >
> >>
> >>
> >>
> >> --
> >> Dave Täht
> >>
> >> Fixing bufferbloat with cerowrt:
> >> http://www.teklibre.com/cerowrt/subscribe.html
> >
> >
>
>
>
> --
> Dave Täht
>
> Fixing bufferbloat with cerowrt:
> http://www.teklibre.com/cerowrt/subscribe.html
>
[-- Attachment #2: Type: text/html, Size: 3960 bytes --]
next prev parent reply other threads:[~2014-02-09 22:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-09 4:35 Dave Taht
2014-02-09 5:16 ` Outback Dingo
2014-02-09 5:17 ` Outback Dingo
2014-02-09 10:59 ` Outback Dingo
2014-02-09 17:56 ` Dave Taht
2014-02-09 20:24 ` Dave Taht
2014-02-09 22:07 ` Outback Dingo
2014-02-09 22:08 ` Outback Dingo
2014-02-09 22:13 ` Dave Taht
2014-02-09 22:14 ` Outback Dingo [this message]
2014-02-09 22:27 ` Dave Taht
2014-02-09 22:13 ` Outback Dingo
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=CAKYr3zz+3CAqyihm-tmMc7LK7wMYxCkFOb9OfOxYCd-Z5MdHuA@mail.gmail.com \
--to=outbackdingo@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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