On 06/14/2016 04:51 PM, Henrique de Moraes Holschuh wrote:
>
> And if such a module blacklist feature ends up being invoked by the
> "nuke_module_from_orbit=" parameter, I will pay the author
> (and the subsystem maintainer that manages to get that merged) a couple
> beers should we ever meet i
On Tue, 14 Jun 2016, Christoph Hellwig wrote:
> On Mon, Jun 13, 2016 at 08:32:41AM -0400, Prarit Bhargava wrote:
> > Blacklisting a module in linux has long been a problem. The process of
> > blacklisting a module has changed over time, and it seems that every OS
> > does it slightly differently a
On 06/14/2016 01:17 PM, Christoph Hellwig wrote:
> On Mon, Jun 13, 2016 at 08:32:41AM -0400, Prarit Bhargava wrote:
>> Blacklisting a module in linux has long been a problem. The process of
>> blacklisting a module has changed over time, and it seems that every OS
>> does it slightly differently
On Mon, Jun 13, 2016 at 08:32:41AM -0400, Prarit Bhargava wrote:
> Blacklisting a module in linux has long been a problem. The process of
> blacklisting a module has changed over time, and it seems that every OS
> does it slightly differently and depends on the age of the init system
> used on tha
Prarit Bhargava writes:
> Blacklisting a module in linux has long been a problem. The process of
> blacklisting a module has changed over time, and it seems that every OS
> does it slightly differently and depends on the age of the init system
> used on that OS.
Hi Prarit,
I don't mind
Blacklisting a module in linux has long been a problem. The process of
blacklisting a module has changed over time, and it seems that every OS
does it slightly differently and depends on the age of the init system
used on that OS.
The current Fedora/systemd procedure is to use rd.blacklist=module
