public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Jim McCloskey <mcclosk@ucsc.edu>
Cc: linux-kernel@vger.kernel.org, rusty@rustcorp.com.au
Subject: Re: net-pf-10, 2.6.1
Date: Sun, 1 Feb 2004 09:59:06 +0000	[thread overview]
Message-ID: <20040201095906.A15264@flint.arm.linux.org.uk> (raw)
In-Reply-To: <E1AnDuR-0000Jj-00@toraigh>; from mcclosk@ucsc.edu on Sun, Feb 01, 2004 at 01:28:55AM -0800

On Sun, Feb 01, 2004 at 01:28:55AM -0800, Jim McCloskey wrote:
> I've tried the variations I can think of---putting the line:
> 
>    install net-pf-10 /bin/true
> 
> in /lib/modules/modprobe.conf via update-modules, or directly by hand-editing.

The first thing to note is that the kernel tries to insert modules
for non-existent network protocols by calling modprobe with net-pf-N
where N is the protocol number.  N=10 for IPv6.

>    ohlone#  modprobe net-pf-10
>    FATAL: Module ipv6 not found.
> 
> indicating that modprobe knows about the alias, but is not running
> /bin/true when requested to load the module.

... because the module is now known as ipv6 not net-pf-10.

> However: if I manually edit /etc/modprobe.d/aliases (which you're not
> supposed to do), so as to comment out:
> 
>   # alias net-pf-10 ipv6
> 
> and then add:
> 
>   install ipv6 /bin/true

You've made two changes at the same time - no wonder you're getting
confused.  In the first change, you've told it to no longer alias
net-pf-10 to ipv6, so it won't go anywhere near "ipv6" anymore.  In
the second change, you've told it to use /bin/true to insert the ipv6
module - which it doesn't find because its still looking for "net-pf-10"

Golden rule: only make one change at a time.

Here's the practical examples showing what's going on:

[root@cps /root]# cat /etc/modprobe.conf
[root@cps /root]# modprobe net-pf-10
FATAL: Module net_pf_10 not found.
[root@cps /root]#

---

[root@cps /root]# cat /etc/modprobe.conf
alias net-pf-10 ipv6
[root@cps /root]# modprobe net-pf-10
FATAL: Module ipv6 not found.
[root@cps /root]#

---

[root@cps /root]# cat /etc/modprobe.conf
alias net-pf-10 ipv6
install net-pf-10 /bin/true
[root@cps /root]# modprobe net-pf-10
FATAL: Module ipv6 not found.
[root@cps /root]#

---

[root@cps /root]# cat /etc/modprobe.conf
alias net-pf-10 ipv6
install ipv6 /bin/true
[root@cps /root]# modprobe net-pf-10
[root@cps /root]#


-- 
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

  parent reply	other threads:[~2004-02-01  9:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-01  9:28 net-pf-10, 2.6.1 Jim McCloskey
2004-02-01  9:46 ` Kiko Piris
2004-02-01 20:31   ` Jim McCloskey
2004-02-01  9:59 ` Russell King [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-30  8:36 root
2004-01-30  8:51 ` Russell King
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

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=20040201095906.A15264@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcclosk@ucsc.edu \
    --cc=rusty@rustcorp.com.au \
    /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