From: Samium Gromoff <deepfire@sic-elvis.zel.ru>
To: ml@basmevissen.nl
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Shut up about the damn modules already...
Date: Fri, 13 Feb 2004 20:38:19 +0300 [thread overview]
Message-ID: <87lln6op6c.wl@canopus.ns.zel.ru> (raw)
> Rusty Russell wrote:
>
> > Please apply before 2.6.3.
> >
> > In almost all distributions, the kernel asks for modules which don't
> > exist, such as "net-pf-10" or whatever. Changing "modprobe -q" to
> > "succeed" in this case is hacky and breaks some setups, and also we
> > want to know if it failed for the fallback code for old aliases in
> > fs/char_dev.c, for example.
> >
> > Just remove the debugging message which fill people's logs:
>
> Yup, those messages are really annoying.
>
> I'm wondering why it is that the kernel is asking for non-existing
> modules so often. Is it that userspace applications try to access all
> kinds of devices too often (autoprobing) or it this (wanted) kernel
> behaviour?
>
> If it is the former, I think that applications should be fixed in the
> first place. Maybe userspace and kernel should share knowledge about
> what devices are there and supported by the kernel(modules).
>
> 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?
> Regards,
>
> Bas.
regards, Samium Gromoff
next reply other threads:[~2004-02-13 17:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 17:38 Samium Gromoff [this message]
2004-02-13 19:41 ` [PATCH] Shut up about the damn modules already Russell King
-- 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=87lln6op6c.wl@canopus.ns.zel.ru \
--to=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