How NOT to have already compiled modules (auto)load?

[Kalin KOZHUHAROV]

Sorry for the fuzzy subject, I couldn't formulate it better.

I was trying to find info on that on Google, man and Documentation/*, but to no avail...

I have a laptop with USB CD-ROM that is very rarely attached/used.
I have sr_mod, etc. compiled as modules.
On every boot it gets autoloaded, despite the fact that CD-ROM is not connected (no, I don't have another).

My question is is there any good(tm) way to prevent this?
One way I could think is to rename the module, but that is a bit bad.
Is there a way to blacklist some modules?

Or even better, to be able to manually modprobe (insmod) the so called blacklisted ones, but any other means to load them (such as dependency of another module, loaded by modprobe) should fail?

Another example is the ipv6, which is difficult to unload at best, as sometimes I want to test something without ipv6.

Any help and/or pointers are welcome!

I am subscribed here, please do NOT CC me for the sake of less traffic.

Kalin.

--
||///_ o  *****************************
||//'_/>     WWW: http://ThinRope.net/
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/