public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: root <root@ohlone.ucsc.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: net-pf-10, 2.6.1
Date: Fri, 30 Jan 2004 08:51:36 +0000	[thread overview]
Message-ID: <20040130085136.C9894@flint.arm.linux.org.uk> (raw)
In-Reply-To: <E1AmU8a-00005E-00@localhost>; from root@ohlone.ucsc.edu on Fri, Jan 30, 2004 at 12:36:28AM -0800

On Fri, Jan 30, 2004 at 12:36:28AM -0800, root wrote:
> Is there any guidance about this little annoyance yet? Most of the
> advice I've seen (on other lists) suggests putting the following in
> modprobe.conf:
> 
>    install net-pf-10 /bin/true

You want:

	alias net-pf-10 off

> Almost all of the error messages from modprobe come exactly on the
> heels of a call from cron to run exim. But why should exim spawn an 
> attempt to load this module? And why just with kernel 2.6.1?

Because its trying to see if the kernel supports IPv6 by creating an
IPv6 socket.  Since the IPv6 module is not available, it correctly
fails and uses IPv4 instead.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core

  reply	other threads:[~2004-01-30  8:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-30  8:36 net-pf-10, 2.6.1 root
2004-01-30  8:51 ` Russell King [this message]
2004-01-31 17:00 ` Greg Norris
     [not found] ` <Pine.LNX.4.44.0401301532260.9270-100000@gaia.cela.pl>
2004-01-31 23:35   ` Jim McCloskey
2004-02-01  2:21     ` Steve Youngs
  -- strict thread matches above, loose matches on Subject: below --
2004-02-01  9:28 Jim McCloskey
2004-02-01  9:46 ` Kiko Piris
2004-02-01 20:31   ` Jim McCloskey
2004-02-01  9:59 ` Russell King

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=20040130085136.C9894@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@ohlone.ucsc.edu \
    /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