Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Gabriel Kerneis <kerneis@pps.jussieu.fr>
To: Denis Ovsienko <infrastation@yandex.ru>
Cc: babel-users <babel-users@lists.alioth.debian.org>,
	cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Babel-users] switching cerowrt to quagga-babeld issues
Date: Tue, 3 Jul 2012 14:47:34 +0200	[thread overview]
Message-ID: <20120703124734.GA6910@rhodium.pps.jussieu.fr> (raw)
In-Reply-To: <751571341318910@web30g.yandex.ru>

On Tue, Jul 03, 2012 at 04:35:10PM +0400, Denis Ovsienko wrote:
> > Does anybody know where this difference comes from?
> 
> The difference comes from NetworkManager. […] Would it be better to add a
> watchdog shell script, which does the same, or patch the kernel?

It would be better to remove NetworkManager ;-)

-- Gabriel

P.S. I do understand that it wouldn't solve the issue, just kidding.

  reply	other threads:[~2012-07-03 12:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAA93jw40kiOwDnOzG-_jUn7nKpky59bNBTec8ynjVwJJhKxr0Q@mail.gmail.com>
     [not found] ` <2187151341044351@web9d.yandex.ru>
     [not found]   ` <7isjdcpm1q.fsf@lanthane.pps.jussieu.fr>
     [not found]     ` <40851341093226@web25d.yandex.ru>
     [not found]       ` <7ik3yoz7p2.fsf@lanthane.pps.jussieu.fr>
     [not found]         ` <CAA93jw5p9EqoK09Y_AXaHG_DfH-u_QDYU_FKOK_hhxBRDcuqAA@mail.gmail.com>
     [not found]           ` <1521341229978@web13h.yandex.ru>
2012-07-02 15:36             ` Dave Taht
2012-07-02 16:16               ` L. Aaron Kaplan
2012-07-02 16:44                 ` Dave Taht
2012-07-02 16:54                   ` L. Aaron Kaplan
2012-07-02 17:13                 ` [Cerowrt-devel] DLEP [was: switching cerowrt to quagga-babeld issues] Juliusz Chroboczek
2012-07-02 17:36                   ` [Cerowrt-devel] [Babel-users] " Henning Rogge
2012-07-02 19:50                   ` [Cerowrt-devel] " L. Aaron Kaplan
2012-07-02 20:54               ` [Cerowrt-devel] [Babel-users] switching cerowrt to quagga-babeld issues Denis Ovsienko
2012-07-03  8:10                 ` Denis Ovsienko
2012-07-03 12:35                   ` Denis Ovsienko
2012-07-03 12:47                     ` Gabriel Kerneis [this message]
2012-07-03 13:18                     ` Dave Taht
2012-07-03 14:14                       ` [Cerowrt-devel] " Denis Ovsienko
2012-07-06 16:36                         ` [Cerowrt-devel] [Babel-users] " Denis Ovsienko
2012-07-06 16:52                           ` [Cerowrt-devel] IPv6 RA and RTPROT_whatever [was: switching cerowrt to quagga-babeld issues] Juliusz Chroboczek
2012-07-03 19:17                       ` [Cerowrt-devel] [Babel-users] switching cerowrt to quagga-babeld issues Jim Gettys
2012-07-06 16:59                       ` David Lamparter
2012-07-07 15:53                         ` dpreed
2012-07-03 15:28                     ` Robert Bradley
2012-07-03 15:55                       ` Robert Bradley
2012-07-04 11:34               ` Denis Ovsienko
2012-07-05 14:15                 ` dpreed

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=20120703124734.GA6910@rhodium.pps.jussieu.fr \
    --to=kerneis@pps.jussieu.fr \
    --cc=babel-users@lists.alioth.debian.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=infrastation@yandex.ru \
    /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