From: "Richard E. Brown" <richb.hanover@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] if you can't tell
Date: Thu, 14 Nov 2013 14:36:16 -0500 [thread overview]
Message-ID: <C87EDDB4-746D-4108-934E-1B090BAC00E4@gmail.com> (raw)
In-Reply-To: <CAA93jw48vbded_-Pn6de8P6j+=Oz0DgU-Xw5nM30L-a-hHmEPg@mail.gmail.com>
Dave,
The flurry of comments on 3.10.18 that I posted were partially caused because I used sysupgrade (the first time ever! Previously, I had used tftp.) and I think some problems were caused because I kept the configuration. I’m looking for a bit of time to re-flash, this time not keeping the configs and running my config.sh script to set things up.
Rich
PS I don’t see a 3.10.19 posted on http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/ yet.
On Nov 14, 2013, at 2:04 PM, Dave Taht <dave.taht@gmail.com> wrote:
> I am simply horribly, horribly behind on email. I just got back from
> canada day before yesterday and am trying to dig out. IETF was both
> productive and non-productive in many ways...
>
> was the consensus 3.10.18 was busted worse than 3.10.17? .19 is out
> but I'll sink more time into it overall to solve various bugs
> (sysupgrade via gui works? but not at the command line?) once and for
> all, rather than
> keep integrating
>
> --
> 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
next prev parent reply other threads:[~2013-11-14 19:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 19:04 Dave Taht
2013-11-14 19:31 ` Sebastian Moeller
2013-11-14 19:36 ` Richard E. Brown [this message]
2013-11-14 19:57 ` Dave Taht
2013-11-14 20:11 ` Sebastian Moeller
2013-11-17 21:59 ` Sebastian Moeller
[not found] <52852256.3010401@imap.cc>
2013-11-14 19:20 ` Fred Stratton
2013-11-14 19:21 ` Fred Stratton
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=C87EDDB4-746D-4108-934E-1B090BAC00E4@gmail.com \
--to=richb.hanover@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