From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] Bug #360 stomped, 3.3.2-8 is out
Date: Sat, 21 Apr 2012 10:11:51 -0700 [thread overview]
Message-ID: <CAA93jw4JRVSOhGO-imr1vYktu=2-oGfFgOAwsvAy7r+OFjsywA@mail.gmail.com> (raw)
It's at:
http://huchra.bufferbloat.net/~cero1/3.3/3.3.2-8/
+ http://www.bufferbloat.net/issues/360#note-85 stomped
+ tcsh,python packages added back in
+ openssl cve (security problem) fixed
I recommend people upgrade to this release, not just for the
performance fixes, but in light of the openssl problem.
I have updated the portions of the web site that I'm aware of to point
to 3.3.2-8 as the default build now.
I have two bugs left to fix to be 'feature complete', and I have some
conflicting work to do on another project, so I hope this release
holds up for a while. Notably a replacement for the QoS system (it's
called 'AQM', and I'd like to make sure that links and pointers start
pointing at 'AQM' or 'AQM/QoS' rather than just straight QoS...
)...
and @!#!@ dhcp-pd.
I am VERY tempted to do 'one last pull' from the openwrt mainline.
They too are now up to 3.3.2, there are some wireless fixes in there
that I haven't got, a few package upgrades (I cherry picked the
openssl fix from them), and I figure the final patch in bug #360 will
make it up to them after a little more testing.
I am so delighted to see buildbot is back to working on this
architecture, automated integration is now PERFECT...
http://buildbot.openwrt.org:8010/builders/ar71xx
:me wipes away stress generated tear:
So I may do that merge...
but not until AFTER I get my last two features done.
Similarly, I expect kernel 3.3.3 to be out fairly soon and I can drop
much of the patch burden.
I would be very interested to have some benchmarks come back on samba,
polipo proxy, and vpn technologies now that cero is running as fast
and as smoothly as seems possible!
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net
reply other threads:[~2012-04-21 17:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAA93jw4JRVSOhGO-imr1vYktu=2-oGfFgOAwsvAy7r+OFjsywA@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-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