From: Dave Taht <dave.taht@gmail.com>
To: Hector Ordorica <hechacker1@gmail.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] patches, build sources?
Date: Mon, 1 Aug 2011 13:40:11 -0600 [thread overview]
Message-ID: <CAA93jw5Re4_vSsa6Hr8KpLRF6yBBYpwKBby3orps5JUyyynP_Q@mail.gmail.com> (raw)
In-Reply-To: <CAMNY_1WX1JpGhTg3sOJydtHDdHrwXPAEjr3S2D1wobvVSS+-YQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2641 bytes --]
Dear Hector:
We're getting to where all the sources will be publicly available via a
simple build script. Regrettably the script and repos have cleanup problems
right now that I hope to solve by Friday, and I plan to push out a few of
the main patches into openwrt in that timeframe as well. There are only a
few left, actually, most everything is already in openwrt.
Whenever we've got a build script debugged, it will be up at:
http://www.bufferbloat.net/projects/cerowrt/wiki/Building_Cerowrt_on_your_own_machine
If it weren't for the progress being made on this bug:
http://www.bufferbloat.net/issues/216
We would have announced rc4 as the first viable beta candidate today.
We would sure like a few friends and family to further check rc4 out, but at
the moment, before going beta, we may have to do a rc5 and rc6.
As it is:
Some documentation on what we are trying to do with cerowrt as a means to
solve many endemic problems of the internet (not just bufferbloat!) is at:
http://cero2.bufferbloat.net/cerowrt
Preliminary release notes and installation guide:
http://www.bufferbloat.net/projects/cerowrt/wiki
The bug list:
http://www.bufferbloat.net/projects/cerowrt/issues
And rc4 (for the NETGEAR wndr3700v2 ONLY) is at:
http://huchra.bufferbloat.net/~cero1/cerowrt-wndr3700-1.0rc4/
I would still call this a 'friends and family' release - please feel free to
download and try it, and file bugs but don't bet your business on it. It's
intended more as a research platform than anything else.
more news as it happens!
On Thu, Jul 28, 2011 at 5:26 PM, Hector Ordorica <hechacker1@gmail.com>wrote:
> Hello bufferbloat mailing list.
>
> So I've asked the past 2 days in IRC about where I can get the
> patches/kernel/build of cerowrt so I can hack on it.
>
> Unfortunately, I'm not in the IRC room at the same time as a lot of
> you (and I don't idle). So no replies yet.
>
> Preferably I'd like to get a hold of the de-bufferbloat patches that I
> can apply on top of OpenWRT. But using cero as a base is fine too.
>
> There's just a few things I'd like to include/change in the kernel.
> Plus the list of third-party software packages isn't that extensive
> from the cerowrt sources.
>
>
> I've looked around the wiki, but can't find the sources. Is it not public?
>
> Thanks if you could direct me.
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com
[-- Attachment #2: Type: text/html, Size: 3919 bytes --]
prev parent reply other threads:[~2011-08-01 18:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 23:26 Hector Ordorica
2011-08-01 19:40 ` Dave Taht [this message]
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw5Re4_vSsa6Hr8KpLRF6yBBYpwKBby3orps5JUyyynP_Q@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=hechacker1@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