Hi Dave,
On Aug 13, 2013, at 22:33 , Dave Taht <dave.t...@gmail.com> wrote:
> On Tue, Aug 13, 2013 at 12:40 PM, Fred Stratton <fredstrat...@imap.cc> wrote:
>
>>>
>>> DT has taken to stealth with his releases.
>
> Heh. No, these are not releases. If I don't get a chance to do some
> testing I don't post their existence to the list.
>
> I don't mind people being eager and willing to test 'em without me
> doing so, tho.
>
> To explain, I do what's called "continuous integration" whenever
> possible (see wikipedia)
Ah, understood, I guess continuous testing works well with this
approach :)
>
> Big triggers for that are new kernel releases (like 3.10.6), fixes
> like the boatload that felix just landed for the ethernet and the wifi
> aggregation rework, and tossing in a new version of the codel patches,
> and tossing in the AQM stuff that sebastian just did - and all that
> landed in 3.10.6-1.
>
> Merely getting this stuff to compile is often a chore. In fact, it
> took me all day to get all that to work... and my only spare router I
> dare sacrifice (the other 4 in the testbed are doing some benchmarks
> as I write) is still in my suitcase and in the car.
>
> Usually I get around to announcing a "development release" once it's
> been tested for a little while, at least a quick check, and preferably
> a couple hours under heavy load, and usually that will be at least a
> -3. I generally try to stay away from X.Y.0 and wait for X.Y.1...
>
> We still have a few things left to fold into this kernel - notably the
> new htb patches from jesper and to backport a few other fixes from
> net-next, and it looks like the changes to the AQM thing need a
> smarter radio box in the gui(?).
Ah, yes, I was looking for radio buttons initially came up blank, then
failed to get LUCI's :depends mechanism work properly and just resorted to
exposing both checkboxes. Far from ideal, I guess in the next iteration I will
just have a drop down bow with "none", "htb", "stab" then it will be
unambiguous.
> I'm also trying to freeze the ubnt
> picostation and nanostation on the same stuff (and what's causing even
> more delay is trying to get a guruplug and edgerouter booted with it
> too. I've always resisted expanding the scope of the cerowrt project
> to more hardware, but I need two higher power boxes to drive some
> tests with desperately)
More hardware, more pain? I wonder, have you found a successor to the
WNDR3[7|8]00 yet?
>
> I'm off to do my laundry in a bit, and will return with fresh clothes
> and that router this evening.
>
> I would very much like to get to a new "stable" release this month,
> it's been far too long since the last one! But to do that we have to
> have zero crash bugs
Okay, not that it is conclusive, but 3.10.1-1did not crash on me once.
> , and be "feature complete". I think we are close
> to zero crashes (but felix fiddling with the ethernet and the wifi
> recently scares me and I still haven't checked to see if sysupgrade
> worked in a couple releases (I flash via tftp usually)), but there are
> some nagging features that I'd like to get in there.
So are Felix changes already in 3.10.6? If so I will ahead and try to
sysupgrade it (I always can fall back to TFTP even if it is a bit inconvenient
due to positioning the router above my reach :) )
> Like this one.
> Keep plugging away, please.
>
> Are there any other must-have features for this puppy? I've been
> looking over gargoyle's ACC code in particular.
Many Thanks & Best Regards
Sebastian
>
>>>
>>>>
>>>> So 3.10.6-1 fails with sysupgrade?
>>>>
>>>> best
>>>> Sebastian
>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Cerowrt-devel mailing list
>>>>> Cerowrt-devel@lists.bufferbloat.net
>>>>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>>>>
>>>
>>
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
>
>
> --
> Dave Täht
>
> Fixing bufferbloat with cerowrt:
> http://www.teklibre.com/cerowrt/subscribe.html
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
_______________________________________________
Cerowrt-devel mailing list
Cerowrt-devel@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/cerowrt-devel
