From: "David S. Miller" <davem@redhat.com>
To: jjs@tmsusa.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: named vs 2.5.64-mm5
Date: Wed, 12 Mar 2003 14:29:51 -0800 (PST) [thread overview]
Message-ID: <20030312.142951.76164766.davem@redhat.com> (raw)
In-Reply-To: <3E6FB472.20809@tmsusa.com>
From: jjs <jjs@tmsusa.com>
Date: Wed, 12 Mar 2003 14:28:02 -0800
So, the SO_BSDCOMPAT messages are in all
likelihood unrelated to the problems I'm seeing
with bind-9.2.1 under 2.5.6x-recent kernels...
I guess I'll have to turn up the debugging on
bind and see if anything unusual pops up -
If bind errors internally because it cannot
set SO_BSDCOMPAT, this is likely the problem.
You need to hack the bind sources to remove references
to SO_BSDCOMPAT.
next prev parent reply other threads:[~2003-03-12 22:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 18:29 named vs 2.5.64-mm5 jjs
2003-03-12 19:31 ` Andrew Morton
2003-03-12 21:16 ` David S. Miller
2003-03-12 22:28 ` jjs
2003-03-12 22:29 ` David S. Miller [this message]
2003-03-12 22:31 ` jjs
-- strict thread matches above, loose matches on Subject: below --
2003-03-12 19:19 Felipe Alfaro Solana
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=20030312.142951.76164766.davem@redhat.com \
--to=davem@redhat.com \
--cc=jjs@tmsusa.com \
--cc=linux-kernel@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