Re: How to prevent modules from being loaded

2004-08-31 Thread Roland Stigge
On Tue, 2004-08-31 at 13:00, Sven Luther wrote:
a while ago, I asked the kernel maintainer how to prevent modules 
from being loaded since now we have hotplug etc. that loads 
everything that sticks to the kernel. 
  
   Using hotplug or discover* blacklists?
  
  I'm using hotplug. Adding snd or snd_intel8x0 to /etc/hotplug/blacklist
  or /etc/hotplug/blacklist.d/local doesn't help here. All the snd modules
  are loaded after bootup as before. 
 
 Like said, there are three things involved here : discover*

There's no discover* on this machine. So no danger from this direction.
Right?

 hotplug

Done.

 magic also module loading.

Which magic do you mean? Please teach me some. :)

Thanks.

bye,
  Roland




Re: How to prevent modules from being loaded

2004-08-31 Thread Sven Luther
On Tue, Aug 31, 2004 at 12:34:57PM +0200, Roland Stigge wrote:
 Hi,
 
 thanks for your reply.
 
 Francesco P. Lovergine wrote:
   a while ago, I asked the kernel maintainer how to prevent modules 
   from being loaded since now we have hotplug etc. that loads 
   everything that sticks to the kernel. 
 
  Using hotplug or discover* blacklists?
 
 I'm using hotplug. Adding snd or snd_intel8x0 to /etc/hotplug/blacklist
 or /etc/hotplug/blacklist.d/local doesn't help here. All the snd modules
 are loaded after bootup as before. 

Like said, there are three things involved here : discover*, hotplug and the
magic also module loading.

You have to do blacklisting in all of them.

Friendly,

Sven Luther




Re: How to prevent modules from being loaded

2004-08-31 Thread Sven Luther
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




Re: How to prevent modules from being loaded

2004-08-31 Thread Roland Stigge
On Tue, 2004-08-31 at 15:06, 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.

Where?


atari:/usr/lib/debootstrap# grep -r discover *
atari:/usr/lib/debootstrap#

atari:/home/ernie/temp# debootstrap sid sid ftp://sbo/debmirror/debian/
[...]
atari:/home/ernie/temp# chroot sid
atari:/# dpkg -l '*discover*'
No packages found matching *discover*.
atari:/#


What does this mean?





How to prevent modules from being loaded

2004-08-30 Thread Roland Stigge
Hi,

a while ago, I asked the kernel maintainer how to prevent modules from
being loaded since now we have hotplug etc. that loads everything that
sticks to the kernel.

He taught me to set an alias to some nonexistent device. An ugly hack,
but it worked.

Now, not even this works for me:

alias snd xxx

leads to snd being loaded at boot time, but later I get:
# modprobe snd
FATAL: Module xxx not found.
#

So I need a new solution.

Any idea?

Thanks.

bye,
  Roland




Re: How to prevent modules from being loaded

2004-08-30 Thread Francesco Paolo Lovergine
On Mon, Aug 30, 2004 at 10:46:50PM +0200, Roland Stigge wrote:
 Hi,
 
 a while ago, I asked the kernel maintainer how to prevent modules from
 being loaded since now we have hotplug etc. that loads everything that
 sticks to the kernel.
 

Using hotplug or discover* blacklists?

-- 
Francesco P. Lovergine