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 11:43:59 +0200 [thread overview]
Message-ID: <aec7e5c3050409024365d724dd@mail.gmail.com> (raw)
In-Reply-To: <E1DK4zA-0005rr-00@gondolin.me.apana.org.au>
On Apr 9, 2005 3:42 AM, Herbert Xu <herbert@gondor.apana.org.au> wrote:
> Magnus Damm <magnus.damm@gmail.com> wrote:
> >
> > 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
>
> Perhaps your favourite distribution could build that as a module to
> start with.
Right. Today distributions can boot from external usb-storage devices,
maybe even from firewire hardware as I am sure you know. I guess they
have support for a device built-in for a reason. I think most
distributions have as streamlined kernels as possible with much code
built as modules - but they would still need some code built-in in the
kernel to have a generic kernel that supports a lot of block devices.
So I think my patch still have a value.
In my case a firewire phy is broken - and, yes - I should fix my
hardware instead of moaning about it here...
Thanks,
/ magnus
next prev parent reply other threads:[~2005-04-09 9:44 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 [this message]
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=aec7e5c3050409024365d724dd@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.