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
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
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
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?
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
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
6 matches
Mail list logo
