All of lore.kernel.org
 help / color / mirror / Atom feed
From: Magnus Damm <magnus.damm@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: rddunlap@osdl.org, 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: Sat, 9 Apr 2005 12:14:42 +0200	[thread overview]
Message-ID: <aec7e5c305040903142cf51f50@mail.gmail.com> (raw)
In-Reply-To: <20050409100702.GA6148@gondor.apana.org.au>

On Apr 9, 2005 12:07 PM, Herbert Xu <herbert@gondor.apana.org.au> wrote:
> On Sat, Apr 09, 2005 at 12:03:45PM +0200, Magnus Damm wrote:
> >
> > > Perhaps they should start using initramfs then.
> >
> > But how does that help me? I still want to be able to pass a list of
> > unwanted modules on the kernel command line. Using initramfs and
> > modules is fine, although I would prefer being able to unload built-in
> > modules instead - but that is another story. Your suggestion just
> > pushes the problem to user space. I think the best alternative would
> 
> Well you know what they say:
> 
> If it can be done in user space, then do it in user space.
> 
> Once the drivers are put on the initramfs it is trivial to add code that
> disables them based on boot-time options.

I agree. And if I understand your opinion correctly you believe that
kernels with built-in modules should not have the feature that my
patch provides, right?

I think it would be a nice feature regardless of initramfs or not.

Thanks for your input!

/ magnus

  reply	other threads:[~2005-04-09 10:14 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
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 [this message]
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=aec7e5c305040903142cf51f50@mail.gmail.com \
    --to=magnus.damm@gmail.com \
    --cc=asterixthegaul@gmail.com \
    --cc=damm@opensource.se \
    --cc=herbert@gondor.apana.org.au \
    --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.