linux-kernel - Re: blacklist kernel boot option

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: <Pine.LNX.4.61.0701291331060.32356@yvahk01.tjqt.qr>
Date:	Mon, 29 Jan 2007 13:40:54 +0100 (MET)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Gerd Hoffmann <kraxel@...e.de>
cc:	linux-kernel@...r.kernel.org
Subject: Re: blacklist kernel boot option


On Jan 29 2007 12:25, Gerd Hoffmann wrote:
>Jan Engelhardt wrote:
>> On Jan 29 2007 09:30, Gerd Hoffmann wrote:
>>> Bernhard Walle wrote:
>>>> * Jan Engelhardt <jengelh@...ux01.gwdg.de> [2007-01-27 15:53]:
>>>> brokenmodules=..., but that's SUSE's linuxrc.
>>> good enough to boot the rescue system from the install cd without
>>> oopsing and fix up the blacklist file in the installed systen though ;)
>> 
>> Does not work with components that are compiled-in, for which such a boot
>> option would be most helpful.
>
>Is that an real-live issue, with distro kernels being shipped with
>almost everything compiled as module these days?

For me it was. FC6 has at least CONFIG_MD=y, and SUSE also has some =y that
could be =m with the help of module autoload rules, and some =y that could
truly be =m. Those being =y cannot be blacklisted.


	-`J'
-- 
-
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/