Re: How to prevent modules from being loaded
On Tue, Aug 31, 2004 at 02:35:13PM +0200, Roland Stigge wrote:
> Hi,
>
> On Tue, 2004-08-31 at 13:11, Sven Luther wrote:
> > > There's no discover* on this machine. So no danger from this direction.
> > > Right?
> >
> > Discover is part of the base system though.
>
> debootstrap doesn't install it, so what do you mean with this?
Sure, it installs discover1.
> > > > magic also module loading.
> > >
> > > Which magic do you mean? Please teach me some. :)
> >
> > i don't know the details, but i believe it is in /etc/init.d/alsa or some
> > other alsa startup scripts.
>
> I'm interested in a more generic way to prevent modules from being
> loaded.
Sure, but this is post-sarge. Please CC debian-kernel on any such issues you
discuss. It is a real mess, and the discover[12]|hotplug|alsa|initrd-tools|whatever
maintainers don't seem in the least interested to solve this correctly. I
myself don't really have the time to followup on this like i would.
> We have achieved a long part of the way towards a universal stock kernel
> image with modules for most setups without the need for manual kernel
> configuration/compilation. But sometimes I need to prevent modules from
> being loaded. E.g. for debugging sessions: Checking bug reports /
> problems without specific subsystems/modules.
Sure.
> Even if it would work, a situation where I need to configure this in 3
> different places violates the SPOT rule [1].
Sure. I have said so in the past, but no real conversation has happened.
Hopefully post-sarge we can solve this.
Friendly,
Sven Luther
Reply to: