lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070127171859.GB10879@strauss.suse.de>
Date:	Sat, 27 Jan 2007 18:18:59 +0100
From:	Bernhard Walle <bwalle@...e.de>
To:	linux-kernel@...r.kernel.org
Subject: Re: blacklist kernel boot option

* Jan Engelhardt <jengelh@...ux01.gwdg.de> [2007-01-27 15:53]:
> 
> On Jan 27 2007 02:22, Florian Schmidt wrote:
> >
> >i was wondering whether there exists any mechanism to blacklist modules
> >from being loaded besides the typical etc/modprobe.d/blacklist type
> >mechanisms. Sometimes you have a module oopsing because of faulty hw
> >which cannot be removed rendering the system unbootable. And sometimes
> >there's just no way to edit the modprobe blacklist because you cannot
> >boot the box :) Basically i would like to setup a list of module names
> >the kernel simply refuses to load..
> >
> >blacklist=some_module,some_other_module,some_third_module
> 
> >Does something exist?
> 
> I think there was something like that although I can't remember
> either what it was.

brokenmodules=..., but that's SUSE's linuxrc.


Regards,
Bernhard
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ