Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Valdis Kletnieks <Valdis.Kletnieks@vt.edu>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] SQM in mainline openwrt, fq_codel considered for fedora default
Date: Tue, 21 Oct 2014 09:57:05 -0700	[thread overview]
Message-ID: <CAA93jw5VtNRC+MCgk1v+dfud7G8vCpHkjZtxQYD6VDEdszgrhA@mail.gmail.com> (raw)
In-Reply-To: <58702.1413908858@turing-police.cc.vt.edu>

[-- Attachment #1: Type: text/plain, Size: 1279 bytes --]

This is not the place to engage in the systemd debate.

We use procd in openwrt because it fits in teeny routers, and it has its
own problems.

I would, in fact, like it if more devs, engaged in auditing, coding for,
and improving *all* the init replacements. The flamage vs fixage ratio
elsewhere is way out of hand, and it bugs me a lot.

The kernel to userspace transition is one of the most finicky, difficult,
and painfully visible areas in which to work, and I would prefer
constructive coding and tips shared here (and elsewhere) between people
trying to make things better at boot, and to work together to make
meaningful change, rather than rehashing old problems and scars.

I note:

I would appreciate some interest from the systemd folk into the work of
ietf  homenet, and into  things like hnetd and mdns proxy. (and the reverse
from those working on those concepts) The excessively dynamic nature of the
modern ipv6 rollout has led to a need to tightly integrate address
assignment,  routing and naming, which helped delay barrier breaker a year
and it's not clear to me to what extent the modern linux server or desktop
can deal with that and still provide useful services, nor concepts like
source specific routing, and better integration with 802.11 and 802.14.

[-- Attachment #2: Type: text/html, Size: 1390 bytes --]

  reply	other threads:[~2014-10-21 16:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-17 18:56 Dave Taht
2014-10-17 19:30 ` Valdis.Kletnieks
2014-10-20 17:03   ` Dave Taht
2014-10-20 17:41     ` Valdis.Kletnieks
2014-10-21 14:50       ` Michal Schmidt
2014-10-21 16:27         ` Valdis.Kletnieks
2014-10-21 16:57           ` Dave Taht [this message]
2014-10-21 17:05             ` Michal Schmidt
2014-10-21 17:24               ` Tom Gundersen
2014-10-21 17:44                 ` Michal Schmidt
2014-10-21 17:52                   ` David Personette
2014-10-21 18:00                   ` Michal Schmidt
2014-10-21 18:06                   ` Tom Gundersen
2014-10-21 19:21                     ` Dave Taht
2014-10-21 19:51                       ` Dave Taht
2014-10-21 20:59                         ` Dave Taht
2014-12-04 16:09                           ` Tom Gundersen
2014-12-04 18:24                             ` Dave Taht
2014-10-21 23:18                 ` Toke Høiland-Jørgensen
2014-12-04 15:05                   ` Tom Gundersen
2014-12-04 15:08                     ` Toke Høiland-Jørgensen

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=CAA93jw5VtNRC+MCgk1v+dfud7G8vCpHkjZtxQYD6VDEdszgrhA@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=cerowrt-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