From: Dave Taht <dave.taht@gmail.com>
To: bismark-devel@lists.bufferbloat.net
Subject: [Bismark-devel] getting ready for capetown
Date: Wed, 4 May 2011 09:32:42 -0600 [thread overview]
Message-ID: <BANLkTikeZ3fd-0MTNo7bF0GJ6jBG4_gV9w@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2366 bytes --]
I will be at Georgia tech May 5-18 to nail down a solid first release of
bismark for the trip to capetown.
In the process of "freezing" for this release I have created various
capetown- subdirs in src on huchra, and am doing a build now. (for want of a
better name for this release, I'm calling it "capetown")
Assuming it builds, the image will be at
http://huchra.bufferbloat.net/~bismark/capetown-wndr3700v2 in about 30
minutes.
Based on the number of bugs I've been finding in the web interface, I did
make a major change to the existing bismark build by updating from the luci
.09 stable branch to the luci .10.
We will need to freeze the core packages in the build by monday or so and
then maintain the capetown fork until some period in the future. I would
like it, given the small distribution of users in this build, if they would
agree to update to the main fork at some point in the near future.
-1) When do the new routers arrive?
0) There are a large number of outstanding bugs that need to be fixed,
marked urgent in the bismark issues database. I would like people to step up
to take ownership and fix them, before I go around assigning work and
flaying people to stay at their keyboards. (I will be available to help fix
all of them but I'm here to *teach* people to fish, not to do the fishing
myself)
It strikes me as a good idea to have a bug hunt meeting on friday morning at
9 or 10AM.
1) Are there any packages in the current build that are not being built in
the default image that need to be built for capetown? The only one I'm aware
of is "time", which struck me as so simple to package up that I'd left it as
an exercise for a new developer several weeks back... where it still lies.
It's in the cerowrt repo at:
https://github.com/dtaht/ceropackages
and can be checked out read-only by default.
Sign up for github, tell me your id, so you can gain commit access and a
lollypop.
2) I've set the default opkg repository to "capetown.bufferbloat.net". If
the bismark team would like to be hosting the package repository somewhere
else, now would be a good time to setup DNS for it, as well as a means of
doing rsync (preferably) and/or scp to a virtual host on the site of your
choice.
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com
[-- Attachment #2: Type: text/html, Size: 2740 bytes --]
reply other threads:[~2011-05-04 15:28 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BANLkTikeZ3fd-0MTNo7bF0GJ6jBG4_gV9w@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bismark-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