SCIENTIFIC-LINUX-USERS Archives

September 2010

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV
Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: stopping dm-* modules and associated files from loading at boot
From:
Akemi Yagi <[log in to unmask]>
Reply To:
Akemi Yagi <[log in to unmask]>
Date:
Tue, 31 Aug 2010 22:10:29 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (27 lines) 
On Tue, Aug 31, 2010 at 8:06 PM, g <[log in to unmask]> wrote:
>> On 08/31/2010 11:33 PM, Akemi Yagi wrote:

>  # mkinitrd --omit-raid-modules --omit-lvm-modules \
>    /boot/initrd-2.6.18-164.11.1.el5.img 2.6.18-164.11.1.el5
>
> dm-* modules load on boot.
>
> added
>
>  blacklist dm-[module names]
>
> to "modprobe.conf", 'dm-*' modules load on boot.
>
> any further suggestions?

I understand mkinitrd would not honor the options if the system sees
certain hardware.

If you are determined to removed those modules, you can do so by:

(1) unpack the initrd.img file (use gunzip and cpio)
(2) delete the modules of your target
(3) repack the modified content into initrd.img

Akemi

ATOM RSS1 RSS2