From: Dave Jones <davej@redhat.com>
To: "Richard B. Johnson" <linux-os@analogic.com>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>,
Magnus Damm <magnus.damm@gmail.com>,
roland@topspin.com, asterixthegaul@gmail.com, damm@opensource.se,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][RFC] disable built-in modules V2
Date: Thu, 7 Apr 2005 13:37:13 -0400 [thread overview]
Message-ID: <20050407173713.GD17485@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0504071319430.5977@chaos.analogic.com>
On Thu, Apr 07, 2005 at 01:22:57PM -0400, Richard B. Johnson wrote:
> >| Anyway, besides nitpicking, is there any reason not to include this
> >| code? Or is the added feature considered plain bloat? Yes, the kernel
> >| will become a bit larger, but all the data added by this patch will go
> >| into the init section.
> >
> >Looks like a good idea to me.
> >
> 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).
Why do you need a module ?
echo 0xFFFEFFFF ?> /proc/sys/kernel/cap-bound
should do this just fine.
Dave
next prev parent reply other threads:[~2005-04-07 17:37 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
2005-04-07 17:37 ` Dave Jones [this message]
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=20050407173713.GD17485@redhat.com \
--to=davej@redhat.com \
--cc=asterixthegaul@gmail.com \
--cc=damm@opensource.se \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=magnus.damm@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox