Advantages of New Module Blacklisting?

cb474 · 2011-06-11 02:14:30

I'm just curious, could someone explain to me what are the advantages of the new method for module blacklisting?

Off hand its seems counter to the Arch keep it simple philosophy, with rc.conf being one centralized place to alter a lot of systems settings, rather than having them fragmented between various different .conf files.

The Arch Linux News post on this alludes to long term benefits for the new method, without describing them. So I'm just wondering what those benefits are. Thanks.

Last edited by cb474 (2011-06-11 02:15:09)

mcmillan · 2011-06-11 03:07:31

My understanding is the old way had become redundant with stuff that modprobe was doing themselves. As user it's probably a little less simple having things spread around, though it becomes simpler for the devs to maintain since they can just rely on upstream.

ngoonee · 2011-06-11 05:51:49

cb474 wrote:

Off hand its seems counter to the Arch keep it simple philosophy, with rc.conf being one centralized place to alter a lot of systems settings, rather than having them fragmented between various different .conf files.

Arch's simplicity was never primarily about the user having things easy . rc.conf is central to Arch-specific settings, and module blacklisting is now possible in /etc/modprobe.d/modprobe.conf, so its not longer an Arch-specific setting.

pogeymanz · 2011-06-11 15:47:55

Just here to +1 ngoonee.

It used to be necessary. Since modprobe now has built in blacklisting, it is no longer necessary for Arch to have its own way. That's simplicity.

cb474 · 2011-06-13 07:53:32

Okay, so it's more consistent with the philosophy of letting packages work how they were intended upstream. I get that.

Are there any benefits to the new way, other than that? Thanks.

ngoonee · 2011-06-13 09:53:59

cb474 wrote:

Okay, so it's more consistent with the philosophy of letting packages work how they were intended upstream. I get that.
Are there any benefits to the new way, other than that? Thanks.

Supposedly faster, but I don't think that's directly a result of this change, more some other cleanups in load-module.sh (not having to deal with blacklisting of course makes things much easier).

You could just go to the ML and read the recent thread on this, you know.

ANOKNUSA · 2011-06-13 22:56:40

The primary benefit is that it avoids the potential detriments of having multiple configs/symlinks/abstract layers of software/whatever vie for control of a particular task. It wasn't intended to make things better, so much as to forestall potential problems.

cb474 · 2011-06-14 23:50:08

Thanks, ANOKNUSA.

Arch Linux

#1 2011-06-11 02:14:30

Advantages of New Module Blacklisting?

#2 2011-06-11 03:07:31

Re: Advantages of New Module Blacklisting?

#3 2011-06-11 05:51:49

Re: Advantages of New Module Blacklisting?

#4 2011-06-11 15:47:55

Re: Advantages of New Module Blacklisting?

#5 2011-06-13 07:53:32

Re: Advantages of New Module Blacklisting?

#6 2011-06-13 09:53:59

Re: Advantages of New Module Blacklisting?

#7 2011-06-13 22:56:40

Re: Advantages of New Module Blacklisting?

#8 2011-06-14 23:50:08

Re: Advantages of New Module Blacklisting?

Board footer