On Sun, May 13, 2007 at 09:23:52AM -0700, Stephen Hemminger wrote: > On Sun, 13 May 2007 16:25:17 +0300 > Dan Aloni <[EMAIL PROTECTED]> wrote: > > > Kernel developers might find it useful for quickly getting out from some > > rough debugging scenarios. > > > > Signed-off-by: Dan Aloni <[EMAIL PROTECTED]> > > > > 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
