On 29 October 2010 13:41, Andrew Harford
<andrew.harford@redbrick.dcu.ie> wrote:
On Fri, Oct 29, 2010 at 11:34:58AM +0100, Cian Brennan wrote:
> I'd like to suggest that in future when we find a bug in any of the kernel
> modules we have no reason to ever use (and there are almost certainly lots of
> these), we blacklist the module from then on. Someone should add a page to docs
> with a list of the modules we have blacklisted, and what they do then, so as to
> make it easier to keep the list across new installs, and so that people can
> figure out what's wrong when we do decide we need one of them.
This is a good idea.
This is a good idea, not sure why we haven't thought of this before :)
There's no reason we couldn't include a modprobe conf in a package, that
would ensure the blacklist stayed consistent across all machines and new
installs.
Is there a reason we need to be able to load modules after boot though?
--
Andrew Harford
Did you hear that Meg? Guys can marry other guys now. So...this is
awkward, but I mean, if they can do that, that is pretty much it for you,
isn't it? I mean you as well pack it in. Game over. --Stewie Griffin