From: Dan Aloni <da-x@monatomic.org>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] allow kernel module exclusion on load
Date: Sun, 13 May 2007 20:15:55 +0300 [thread overview]
Message-ID: <20070513171555.GA27920@localdomain> (raw)
In-Reply-To: <20070513092352.18cd80de@freepuppy>
On Sun, May 13, 2007 at 09:23:52AM -0700, Stephen Hemminger wrote:
> On Sun, 13 May 2007 16:25:17 +0300
> Dan Aloni <da-x@monatomic.org> wrote:
>
> > Kernel developers might find it useful for quickly getting out from some
> > rough debugging scenarios.
> >
> > Signed-off-by: Dan Aloni <da-x@monatomic.org>
> >
>
> There is already the modprobe blacklist ability in user space.
Yes, however the point here is that you can easily (and temporarily)
blacklist a module *manually* from the boot loader without needing to
actually perform a complete and successful boot. Using modprobe's
blacklist requires editing /etc files, and it also doesn't apply
for initrd/initramfs or other system/distribution-specific scripts
that would do hardcoded sequential insmod invocations (for example
on embedded systems that require minimal userspace complexity).
--
Dan Aloni
XIV LTD, http://www.xivstorage.com
da-x (at) monatomic.org, dan (at) xiv.co.il
next prev parent reply other threads:[~2007-05-13 17:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-13 13:25 Dan Aloni
2007-05-13 16:23 ` Stephen Hemminger
2007-05-13 17:05 ` Nikita V. Youshchenko
2007-05-13 17:15 ` Dan Aloni [this message]
2007-05-13 18:04 ` Michael Tokarev
2007-05-13 18:22 ` Dan Aloni
2007-05-13 18:32 ` Michael Tokarev
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=20070513171555.GA27920@localdomain \
--to=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
all inboxes | Powered by JetHome®