On 08/31/2010 04:35 AM, Chris Stevens wrote:
<snip>

> Some suggestions.  First, I think that renaming the dm directory won't 
> do what you want because a "modprobe -a" will rebuild the dependencies 
> with the new directory names.

sounds logical.


> That's just a theory of mine that's unproven.

a good theory, but what would execute "modprobe -a", other than doing so
manually?

while attempting to manually trouble shoot a problem, such as now, i would
not with out as you suggest...

> To defeat this, you would need to move that directory completely out
> /lib/modules tree.


> However, I would make sure you have a backup kernel configured that you
> can boot from if this crashes your startup.

i keep at least 3 old kernels in case of need to fall back that far.


> A less drastic measure to try would be to make a /etc/modprobe.conf file
> with something like this
> 
> alias modulename off

added;

  alias dm-mem-cache.ko off
  alias dm-mod.ko off
  alias dm-log.ko off
  alias dm-region.ko off
  alias dm-messages.ko off
  alias dm-raid45.ko off

to "/etc/modprobe.conf", then ran

  mkinitrd /boot/initrd-2.6.18-164.11.1.el5.img 2.6.18-164.11.1.el5

rebooted, above "dm-*" still loaded.

> blacklist modulename

is there a difference than 'alias * off'?


> see http://wiki.xdroop.com/space/RedHat/Prevent+Module+Loading for the 
> reference of this solution.

read.


> I would think that a raid setup would need to put this stuff on the 
> initial ram disk in case raid is needed to access the boot/root 
> partitions. 

i have no raid installation.


> So a mkinitrd would probably need to be done after making 
> /etc/modprobe.conf.

which i did.


i thank you for your help.

i am open to other suggestions.

even considering using yum to remove all raid files. i would rather
leave as i may setup a raid system after next end of year.



-- 

peace out.

tc,hago.

g
.

****
in a free world without fences, who needs gates.
**
help microsoft stamp out piracy - give linux to a friend today.
**
to mess up a linux box, you need to work at it.
to mess up an ms windows box, you just need to *look* at it.
**
learn linux:
'Rute User's Tutorial and Exposition' http://rute.2038bug.com/index.html
'The Linux Documentation Project' http://www.tldp.org/
'LDP HOWTO-index' http://www.tldp.org/HOWTO/HOWTO-INDEX/index.html
'HowtoForge' http://howtoforge.com/
****