From: Dave Taht <dave.taht@gmail.com>
To: bismark-devel@projectbismark.net,
bloat-devel <bloat-devel@lists.bufferbloat.net>
Subject: Cerowrt RC6 plan
Date: Wed, 24 Aug 2011 19:04:24 -0700 [thread overview]
Message-ID: <CAA93jw6R6Bv--UiGsxm6eV6WnLygm+KUCVnW=HKOu7MG-SzyLw@mail.gmail.com> (raw)
As a core goal of cerowrt is to stay no more than 2 release cycles
behind the kernel mainline, and we're running several weeks behind the
original release date for cerowrt, anyway, updating the kernel past
2.6.39 has been on my mind.
So, thx to the hard work of 'solca', I just got a build of linux 3.0.3
done which thus far appears stable. The only blocker for RC6 that I
have is:
http://www.bufferbloat.net/issues/243
And the problem with ipv6 and TOS irks me. I keep hoping I'm merely
doing something silly, but more eyeballs on:
http://www.bufferbloat.net/issues/243#change-870
would be nice.
So... I hope to get RC6, containing the 3.0.3 kernel and fixed
iptables out by saturday, as I am finished with linuxcon and will be
back in isc's lab by friday. Proving that stable as a base platform
will enable RC7 to be mostly fixes and additions to various utilities.
Numerous other small fixes have gone in as well,
http://www.bufferbloat.net/projects/cerowrt/issues?query_id=5
but many of the more difficult ones - notably gui-related bugs - seem
likely to be unfixable by 1.0. I do hope we can address some more of
the time and dnssec related bugs by RC7, which is tenatively targetted
for sept 5.
http://www.bufferbloat.net/projects/cerowrt/issues?query_id=2
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com
next reply other threads:[~2011-08-25 1:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 2:04 Dave Taht [this message]
2011-08-25 2:18 ` Dave Taht
2011-08-25 20:01 ` Its the bufferbloat stupid Marc Manthey
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='CAA93jw6R6Bv--UiGsxm6eV6WnLygm+KUCVnW=HKOu7MG-SzyLw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bismark-devel@projectbismark.net \
--cc=bloat-devel@lists.bufferbloat.net \
/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