All of lore.kernel.org
 help / color / mirror / Atom feed
From: Magnus Damm <magnus.damm@gmail.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: linux-os@analogic.com, roland@topspin.com,
	asterixthegaul@gmail.com, damm@opensource.se,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] disable built-in modules V2
Date: Thu, 7 Apr 2005 20:53:30 +0200	[thread overview]
Message-ID: <aec7e5c305040711535bbe07d3@mail.gmail.com> (raw)
In-Reply-To: <20050407102925.2ab27740.rddunlap@osdl.org>

On Apr 7, 2005 7:29 PM, Randy.Dunlap <rddunlap@osdl.org> wrote:
> On Thu, 7 Apr 2005 13:22:57 -0400 (EDT) Richard B. Johnson wrote:
> | Can't you disable module-loading with a module? I think so.
> | You don't need to modify the kernel. Boot-scripts could
> | just load the "final" module and there is nothing that
> | can be done to add another module (or even unload existing
> | ones).
> 
> Sounds likely, but that's not what the patch from Magnus is
> even trying to do.  It's purely for boot-time selection of
> troublesome modules or devices AFAICT.  I've had a few
> occasions to use something like this -- or rebuild a kernel
> or remove a device.

Yes, the idea is to be able to disable misbehaving built-in modules
from the kernel command line. The alternative is of course to disable
the code using the kernel configuration system and rebuild the kernel.

Say a kernel shipped with your favourite distribution crashes your
machine during boot-up - wouldn't it be nice to be able to just
disable the problematic module from the kernel command line instead of
(1) getting the config, (2) getting the distribution-specific patches,
(3) rebuilding the kernel. And if you are lucky you need to (0) setup
a cross compiler and (4) get your hands on a suitable initrd.

/ magnus

  reply	other threads:[~2005-04-07 18:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-05 23:29 [PATCH][RFC] disable built-in modules V2 Magnus Damm
2005-04-06 10:32 ` Malcolm Rowe
2005-04-06 13:10   ` Magnus Damm
2005-04-06 14:28     ` Malcolm Rowe
2005-04-06 22:14       ` Magnus Damm
2005-04-07  7:47         ` Zwane Mwaikambo
2005-04-07  1:32 ` AsterixTheGaul
2005-04-07  2:23   ` Roland Dreier
2005-04-07  8:23     ` Magnus Damm
2005-04-07 17:01       ` Randy.Dunlap
2005-04-07 17:22         ` Richard B. Johnson
2005-04-07 17:29           ` Randy.Dunlap
2005-04-07 18:53             ` Magnus Damm [this message]
2005-04-09  1:42               ` Herbert Xu
2005-04-09  9:43                 ` Magnus Damm
2005-04-09  9:48                   ` Herbert Xu
2005-04-09 10:03                     ` Magnus Damm
2005-04-09 10:07                       ` Herbert Xu
2005-04-09 10:14                         ` Magnus Damm
2005-04-07 17:37           ` Dave Jones
2005-04-07  2:38   ` Horst von Brand
2005-04-07 21:33     ` Magnus Damm

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=aec7e5c305040711535bbe07d3@mail.gmail.com \
    --to=magnus.damm@gmail.com \
    --cc=asterixthegaul@gmail.com \
    --cc=damm@opensource.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    --cc=rddunlap@osdl.org \
    --cc=roland@topspin.com \
    /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.