Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] cerowrt-3.10.21-1 development release
Date: Mon, 2 Dec 2013 07:17:55 -0800	[thread overview]
Message-ID: <CAA93jw70diUKqToTbT2dbGd0fMLNNgxEDfQXXYny5csodz9EYg@mail.gmail.com> (raw)
In-Reply-To: <BEC6D716-CD7E-4540-B191-1A3BE3A43AF0@gmx.de>

As best as I recall it was needed for ext4 and btrfs support on
mounting external devices, but that was years ago.

On Mon, Dec 2, 2013 at 2:44 AM, Sebastian Moeller <moeller0@gmx.de> wrote:
> Hi Dave,
>
>
> On Dec 2, 2013, at 02:07 , Dave Taht <dave.taht@gmail.com> wrote:
>
>> This is nothing more than a resync with openwrt and a bugfix for
>> dnsmasq. It is completely untested.
>>
>> + fresh merge with openwrt
>> ++ bunch of ath9k fixes
>> + update to dnsmasq 2.68rc4 (fixes cname and a few other bugs)
>>
>> - haven't found time to address http://www.bufferbloat.net/issues/436
>>   plan to update the machine involved to this version.
>>   hope to get more reports from the field. ? Would like to find someone
>>   with comcast ipv6 to try this on....
>>
>> - the /sbin/mount bug explanation sounded plausible but haven't tried it
>>   will do so shortly
>
>         The quickest test should be to deinstall mount-utils before running sys upgrade (as far as I know mount-utils is the source of the incompatible mount binary). The new cerowrt will automatically bring in its already installed mount-utils, so everything should work after the upgrade. I have not tested this yet, but I assume this is what I'll try the next time :)
>         BTW, what is the reason we need mount-utils in the first place, or what is the busy box mount command missing?
>
> best regards
>         sebastian
>
>>
>> - have several reports of a successful "fragmentation?" crash attack
>>  in openwrt in general, but no details.
>>
>> I'm taking a bunch of machines into the lab thursday and hope to work
>> on the latter problem while putting several new machines/OSes through
>> their paces...  It seemes likely I will do another build between now
>> and thursday.
>>
>> In short, not a lot of reason to try this release. Feel free to keep
>> digesting your turkey.
>>
>> https://www.youtube.com/watch?v=W5_8U4j51lI
>>
>> New version of pie should get dropped next week.
>>
>>
>>
>>
>> --
>> 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

  reply	other threads:[~2013-12-02 15:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-02  1:07 Dave Taht
2013-12-02 10:44 ` Sebastian Moeller
2013-12-02 15:17   ` Dave Taht [this message]
2013-12-02 15:46     ` David Personette
2013-12-08 17:13     ` 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=CAA93jw70diUKqToTbT2dbGd0fMLNNgxEDfQXXYny5csodz9EYg@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=moeller0@gmx.de \
    /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