From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Samium Gromoff <deepfire@sic-elvis.zel.ru>
Cc: ml@basmevissen.nl, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Shut up about the damn modules already...
Date: Fri, 13 Feb 2004 19:41:31 +0000 [thread overview]
Message-ID: <20040213194131.B8188@flint.arm.linux.org.uk> (raw)
In-Reply-To: <87lln6op6c.wl@canopus.ns.zel.ru>; from deepfire@sic-elvis.zel.ru on Fri, Feb 13, 2004 at 08:38:19PM +0300
On Fri, Feb 13, 2004 at 08:38:19PM +0300, Samium Gromoff wrote:
> > In the meantime, your patch needs to go in though because fixing this in
> > userspace is not something that will happen on short term.
> Wouldn`t this remove the last reason to fix the broken software?
I don't believe there's any code which needs fixing in userspace. We just
need modprobe.conf to do the right thing when we convert peoples old
modules.conf files.
The original modprobe defaults to:
alias net-pf-10 off
unless net-pf-10 is explicitly aliased to something else (ipv6). We
therefore just need peoples modprobe.conf files to contain:
install net-pf-10 /bin/true
provided they haven't aliased net-pf-10 to ipv6.
--
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
next prev parent reply other threads:[~2004-02-13 19:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 17:38 [PATCH] Shut up about the damn modules already Samium Gromoff
2004-02-13 19:41 ` Russell King [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-12 3:13 Rusty Russell
2004-02-12 15:13 ` Rik van Riel
2004-02-13 16:51 ` Bas Mevissen
2004-02-13 18:55 ` Chris Wright
2004-02-13 19:38 ` 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=20040213194131.B8188@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=deepfire@sic-elvis.zel.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=ml@basmevissen.nl \
/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