Fedora 19 assistance on modprobe /etc/modprobe.d/ .conf file being ignored

[Rick Stevens]

On 02/28/2014 04:46 PM, Ed Greshko issued this missive:
> On 03/01/14 08:43, Rick Stevens wrote:
>> It wouldn't be. If the device in question is hot-pluggable, then the act
>> of plugging it in after boot would cause the udev stuff to invoke the
>> modprobe. Since the device isn't hot-pluggable (it's there when you boot
>> the machine), then the module must be loaded in the initrd image to be
>> active at boot. Hence the need to run dracut.
>>
>> As far as I know, this has always been the case. If you need the module
>> at boot, you need to have it in the initrd image.
>
> Sure, it probably has been always the case.  I don't know how I came to know that.  And, I don't know how those who don't know it will come to know it.  Apparently, they won't come to know it by reading any available "documentation".   That is the entirety of my point.

Ah, I see. Yes, I don't know that it's documented anywhere that clearly.
The old "/usr/src/doc/kernel-(version)/Documentation/initrd.txt" file
sort of describes it as does the man page for dracut. I'm sure I learned
it long ago when I started building kernels and drivers for some (at the
time) esoteric hardware and now it's "self-evident" to me.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital    ricks at alldigital.com -
- AIM/Skype: therps2        ICQ: 22643734            Yahoo: origrps2 -
-                                                                    -
-   I haven't lost my mind.  It's backed up on tape somewhere, but   -
-                       probably not recoverable.                    -
----------------------------------------------------------------------