From: Mads Christensen <mfc@krycek.org>
To: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: named problems!
Date: 15 Apr 2003 23:23:00 +0200 [thread overview]
Message-ID: <1050441780.10001.7.camel@krycek> (raw)
In-Reply-To: <1050440553.10001.2.camel@krycek>
[-- Attachment #1: Type: text/plain, Size: 759 bytes --]
woups, forgot to mention, this is on 2.5.67-mm3
the 2.4 series dosn't give me any bitchin' :)
On tir, 2003-04-15 at 23:02, Mads Christensen wrote:
> Hey kernel guys!
>
> I know this issue has been delt with (google) but did you ever reach to
> a fix?
>
> Apr 15 22:56:03 krycek kernel: process `rndc' is using obsolete
> setsockopt SO_BSDCOMPAT
>
> Thx in advance
--
========================================================================
| Mads F. Christensen || email: |
| phone: +45 27 47 58 66 || mfc@krycek.org |
| Webdesign Development || www.krycek.org - personal data site |
========================================================================
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-04-15 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-15 21:02 named problems! Mads Christensen
2003-04-15 21:23 ` Mads Christensen [this message]
2003-04-15 23:18 ` J Sloan
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=1050441780.10001.7.camel@krycek \
--to=mfc@krycek.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.