From: Michael Tokarev <mjt@tls.msk.ru>
To: Patrick McHardy <kaber@trash.net>
Cc: netdev@vger.kernel.org
Subject: Re: http://bugzilla.kernel.org/show_bug.cgi?id=6197
Date: Wed, 14 Jun 2006 01:38:18 +0400 [thread overview]
Message-ID: <448F304A.2020808@tls.msk.ru> (raw)
In-Reply-To: <448EE065.9060207@trash.net>
Patrick McHardy wrote:
[]
> He patched his kernel with the IMQ device, which is known to cause all
> kinds of weird problems.
Wich problems? Known to whom?
I was considering using imq for our needs (not done yet), and from the
FAQ at http://www.linuximq.net/faq.html (item #3, "Is it stable?") it
seems there's no problems except of gre tunnels and locally generated
traffic...
Googling for "imq linux problem" shows usual pile of various user
support questions (how to configure.. what did I do wrong.. etc),
but nothing relevant.
So... I'm curious whenever the claim on linuximq.net site about the
stability is true, or there in fact are some real issue...
Thanks.
/mjt
next prev parent reply other threads:[~2006-06-13 21:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-11 12:51 http://bugzilla.kernel.org/show_bug.cgi?id=6197 Andrew Morton
2006-06-13 15:57 ` http://bugzilla.kernel.org/show_bug.cgi?id=6197 Patrick McHardy
2006-06-13 21:38 ` Michael Tokarev [this message]
2006-06-14 14:04 ` http://bugzilla.kernel.org/show_bug.cgi?id=6197 Patrick McHardy
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=448F304A.2020808@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).