Aussie, I realize that is what it is for. I guess it is a matter of taste. If I wanted unseen processes doing configs in the background though, I wouldn't be running slackware, I would run Mandrake/RdHat/SuSe

Hotplug doesn't do any configs - you still do those with modules.conf, and ~/.asoundrc (for alsa), all hotplug does is load the modules based on the hardware it detects - the only conflicts you get arise when you have a buggy module (and you'll get those without hotplug as well), buggy hardware (ditto) or where there are two kernels modules for the device (as in the OSS and ALSA sound modules), and the blacklist file is what you use to resolve those conflicts, since hotplug has been included in slackware I've only had to edit my rc.modules for i2c and lm_sensors.

Okay, this is the very first I've heard of this hotplug/modules/blacklist thing. And I've done a lot of reading and searching about it. Very helpful guys, I'll try it out tonight. Now it makes more sense that I couldn't figure out where the modules were loading from.

Barbara
(who got sound from gxine and kscd last night, so very happy!)