From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-we0-f171.google.com (mail-we0-f171.google.com [74.125.82.171]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 4E9FB200A12 for ; Thu, 5 Apr 2012 20:23:10 -0700 (PDT) Received: by werm1 with SMTP id m1so2306545wer.16 for ; Thu, 05 Apr 2012 20:23:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=Hj6k7GzCbzC1X7WnKJQ1h7rXynVreqINt/oSU1nA2VI=; b=kEOl57Iuk8Ye0V7kRGSUEvbWvPsTwtGH3RGfuCXYRE+gNAKY44AIc7U550mO581ZEE 5ykZESCktWwmX2wvrNXh1rOrQ+HI71JCuQPzr/CRg9+RCO5YbSrjdNo0ReUt0JSKAunG OZuTGfl36iAmQpQ2wNWJ1LecFG77ABvt0qFvVE8JBt8uUBkWuqHiwCan9gWjQMAKJDXL HwuQ4WDucFGiwN5Z2aXmOHpBcoNpFECtXlT006/ImW1xgp+qv5oZhiXdfk6ANJwnaNxh EzbWZqW8SWp1wCMYKevAJJ852e0Yrzkv2H8+ZhE051gWinaZXwaZ9lbhtCTvDZ8YBGQF 3MXw== MIME-Version: 1.0 Received: by 10.180.81.37 with SMTP id w5mr8517391wix.16.1333682588423; Thu, 05 Apr 2012 20:23:08 -0700 (PDT) Received: by 10.223.127.194 with HTTP; Thu, 5 Apr 2012 20:23:08 -0700 (PDT) Date: Thu, 5 Apr 2012 20:23:08 -0700 Message-ID: From: Dave Taht To: cerowrt-devel@lists.bufferbloat.net Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: [Cerowrt-devel] current sources pushed X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Apr 2012 03:23:10 -0000 as best as I can tell the all the current sources for ceropackages, cerowrt-3.3 and cerofiles have been pushed to their respective repos on github. I note that there is still some hackery involved in choosing the right feeds from env/override.list documented elsewhere. So far as I know the only tricky one is ntp, which remains a problem child no matter which dnssec or non-dnssec one you choose. I'm starting a fresh build from scratch and will check the results in the morning. Please feel free to give it a try. -- Dave T=E4ht SKYPE: davetaht US Tel: 1-239-829-5608 http://www.bufferbloat.net