From: Michael Tokarev <mjt@tls.msk.ru>
To: Dan Aloni <da-x@monatomic.org>
Cc: Stephen Hemminger <shemminger@linux-foundation.org>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] allow kernel module exclusion on load
Date: Sun, 13 May 2007 22:32:31 +0400 [thread overview]
Message-ID: <464759BF.5050505@msgid.tls.msk.ru> (raw)
In-Reply-To: <20070513182226.GA8658@localdomain>
Dan Aloni wrote:
[]
> Yes, I guess a shell script can always look at /proc/cmdline with
> relatively minimal complexity.
>
> Anyway, it all boils down to whether there's a developer demand
> for a userspace-independent way of blacklisting modules. Let's see
> if more people post their opinion so we can determine.
The real problem here - again IMHO - is the complete lack of more-or-less
standard boot sequence. Every distro invents their own intramfs with
unique recognized command-line arguments.
And kinit/klibc doesn't really help here, because it's too low-level.
/mjt
P.S. I wonder why certain emails are duplicated on LKML. An example
is my previous email in this thread - I received two copies of it
from linux-kernel-owner@vger.
next prev parent reply other threads:[~2007-05-13 18:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-13 13:25 [PATCH] allow kernel module exclusion on load Dan Aloni
2007-05-13 16:23 ` Stephen Hemminger
2007-05-13 17:05 ` Nikita V. Youshchenko
2007-05-13 17:15 ` Dan Aloni
2007-05-13 18:04 ` Michael Tokarev
2007-05-13 18:22 ` Dan Aloni
2007-05-13 18:32 ` Michael Tokarev [this message]
2007-05-13 18:20 ` Christoph Hellwig
2007-05-13 18:39 ` Michael Tokarev
2007-05-15 8:23 ` Pavel Machek
2007-05-16 16:51 ` Dan Aloni
2007-05-16 19:33 ` Pavel Machek
2007-05-16 21:09 ` Dan Aloni
2007-05-16 22:00 ` Randy Dunlap
2007-05-15 13:07 ` Andi Kleen
2007-05-14 20:23 ` Valdis.Kletnieks
2007-05-15 8:48 ` Dan Aloni
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=464759BF.5050505@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=da-x@monatomic.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
/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