From: Sebastian Moeller <moeller0@gmx.de>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] just when I thought it was safe to do a release
Date: Wed, 19 Feb 2014 21:32:03 +0100 [thread overview]
Message-ID: <2424A79F-E072-430B-9B2D-00C5BACDE1CF@gmx.de> (raw)
In-Reply-To: <CAA93jw6+Hib-p2SY2XGQ_90Y=Lg2YJo3rvYcE8_SA3Ozc_qq1g@mail.gmail.com>
HI Dave,
On Feb 19, 2014, at 17:29 , Dave Taht <dave.taht@gmail.com> wrote:
> On Wed, Feb 19, 2014 at 11:11 AM, David Personette <dperson@gmail.com> wrote:
>> I installed 3.10.28-12, and other than some missing packages (bash and curl
>
> Heh. What do you guys do, have a cron job polling for changes to the build dir?
> :)
>
> I was going to sit on that and put out a more polished version sometime in
> the next couple days.
>
>> were what I noticed, and pulled from the previous version
>
> I killed some big packages while trying to get a new build done faster.
>
> I'll sort through the missing ones and add them back in. (I also just
> added in squid, per request). Got a big build box donated to use
> again, post disaster.
>
> Does anyone care about cups? (printing?) It was one of those things that
> just barely works in the first place due to memory constraints and a PITA
> and I haven't shipped it in a while. Most printers are network capable
> these days, and what I tend to use the usb port for is odd devices
> and gps and the like. I'd like to have support for a 3g modem or two...
>
> Two concerns of mine are that I killed off udev, which used to manage
> hotplugging. I'd like to know what, if anything, people are using the usb
> for, so as to be able to make sure losing udev doesn't break that…
On my wnder3700v2m I only use the USB to mount a USB stick, for a large persistent /home directory (for cerowrt images mainly, and persistent vnstat data so I can monitor consumed data volume per month) and a swap partition (under the theory that I rather have things slow to molasses while going though paging-purgatory compared to have the rout go belly-up). I have not tested 3.10.20-12 yet, but will holler if mounting the usb stick does not work without udev (but I assume it does not care too much about udev….)
>
>> comcast/3.10.28-4). It's working great for me. Throughput on WiFi from my
>> laptap to wired server is up, from 7-9MB to 10-12MB. Thank you.
>
> I still think there is some tuning to be done on a rrul load, but we had
> to get the last of the instruction traps out of the way first. As of
> this morning
> so far as I know, the "last" ones are gone, but I don't want to jinx it…
Great, so that will be in the next non-release then ;) ?
Best Regards
Sebastian
>
> Did you try ipv6? Default routes are not quite working for me in
> a couple scenarios.
>
>> --
>> David P.
>>
>>
>> On Tue, Feb 18, 2014 at 5:49 PM, Dave Taht <dave.taht@gmail.com> wrote:
>>>
>>> ok, so all the bits flying in loose formation have been rebased on top of
>>> openwrt head, and I've submitted the last remaining differences (besides
>>> SQM) up to openwrt-devel. They immediately took one...
>>>
>>> I also went poking through current 3.14rc kernels to find bugs fixed there
>>> but
>>> not in stable 3.10. Found two more I think. (one elsewhere in the flow
>>> hash that I had
>>> just submitted upstream, sigh). Tried to backport sch_fq and sch_hhf,
>>> failed,
>>> gave up on tracking pie further.
>>>
>>> So I got a new build going, including dnsmasq with dnssec, tested the
>>> components,
>>> and was ready to release...
>>>
>>> ... when a whole boatload of other stuff landed. Doing a new build now...
>>>
>>> and taking the rest of the day off.
>>>
>>>
>>> --
>>> 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
>>
>>
>
>
>
> --
> 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
next prev parent reply other threads:[~2014-02-19 20:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 22:49 Dave Taht
2014-02-19 16:11 ` David Personette
2014-02-19 16:29 ` Dave Taht
2014-02-19 16:38 ` David Personette
2014-02-19 17:01 ` Dave Taht
2014-02-20 5:28 ` Fred Stratton
2014-02-20 9:05 ` Sebastian Moeller
[not found] ` <5305E875.9070508@imap.cc>
2014-02-20 11:35 ` Fred Stratton
2014-02-20 13:15 ` Sebastian Moeller
[not found] ` <5306099C.1090604@xyz.am>
2014-02-20 13:57 ` Fred Stratton
2014-02-20 14:38 ` Sebastian Moeller
2014-02-20 17:24 ` Fred Stratton
2014-02-20 20:08 ` Sebastian Moeller
2014-02-20 20:42 ` Fred Stratton
2014-02-20 22:18 ` Sebastian Moeller
2014-02-21 13:12 ` Rich Brown
2014-02-21 14:17 ` Fred Stratton
2014-02-20 17:49 ` Dave Taht
2014-02-20 18:27 ` Fred Stratton
2014-02-20 20:09 ` Sebastian Moeller
2014-02-19 20:21 ` edwin
2014-02-19 20:32 ` Sebastian Moeller [this message]
2014-02-19 20:43 ` Dave Taht
2014-02-19 21:10 ` Sebastian Moeller
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=2424A79F-E072-430B-9B2D-00C5BACDE1CF@gmx.de \
--to=moeller0@gmx.de \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@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