From: "Brian C. Lane" <bcl@redhat.com>

Anaconda expects a minimum set of modules to be loaded, things
like raid1, etc.

NOTE: Tested by appending to initrd of Beta RC2
---
dracut/Makefile.am | 3 ++-
dracut/anaconda-modprobe.sh | 27 +++++++++++++++++++++++++++
dracut/module-setup.sh | 1 +
3 files changed, 30 insertions(+), 1 deletions(-)
create mode 100644 dracut/anaconda-modprobe.sh

diff --git a/dracut/Makefile.am b/dracut/Makefile.am
index a07060b..2efe38d 100644
--- a/dracut/Makefile.am
+++ b/dracut/Makefile.am
@@ -33,7 +33,8 @@ dist_dracut_SCRIPTS = module-setup.sh
anaconda-copy-ks.sh
fetch-kickstart-net.sh
fetch-kickstart-disk
- parse-kickstart
+ parse-kickstart
+ anaconda-modprobe.sh


MAINTAINERCLEANFILES = Makefile.in
diff --git a/dracut/anaconda-modprobe.sh b/dracut/anaconda-modprobe.sh
new file mode 100644
index 0000000..e3d98ec
--- /dev/null
+++ b/dracut/anaconda-modprobe.sh
@@ -0,0 +1,27 @@
+#!/bin/bash
+# load modules needed by anaconda
+ARCH=$(uname -m)
+KERNEL=$(uname -r)
+
+MODULE_LIST="cramfs squashfs iscsi_tcp"
+
+SCSI_MODULES=/lib/modules/$KERNEL/kernel/drivers/scsi/device_handler/
+for m in $SCSI_MODULES/*.ko; do
+ MODULE_LIST+="`basename $m .ko` "
+done
+
+if [ "$ARCH" != "s390" -a "$ARCH" != "s390x" ]; then
+ MODULE_LIST+="floppy edd iscsi_ibft"
+fi
+
+if [ "$ARCH" = "ppc" ]; then
+ MODULE_LIST+="spufs"
+fi
+
+MODULE_LIST+="raid0 raid1 raid5 raid6 raid456 raid10 linear dm-mod dm-zero
+ dm-mirror dm-snapshot dm-multipath dm-round-robin dm-crypt cbc sha256 lrw xts"
+
+for m in $MODULE_LIST; do
+ modprobe $m
+done
+
diff --git a/dracut/module-setup.sh b/dracut/module-setup.sh
index 2a61c6e..3c0bcbe 100755
--- a/dracut/module-setup.sh
+++ b/dracut/module-setup.sh
@@ -14,6 +14,7 @@ depends() {
install() {
# anaconda
inst "$moddir/anaconda-lib.sh" "/lib/anaconda-lib.sh"
+ inst_hook cmdline 24 "$moddir/anaconda-modprobe.sh"
inst_hook cmdline 25 "$moddir/parse-anaconda-options.sh"
inst_hook cmdline 26 "$moddir/parse-anaconda-kickstart.sh"
inst_hook cmdline 27 "$moddir/parse-anaconda-repo.sh"
--
1.7.7.6

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

> Anaconda expects a minimum set of modules to be loaded, things
> like raid1, etc.
>
> NOTE: Tested by appending to initrd of Beta RC2

Yep, we did this back in the bad old days of loader. I guess we do need
to keep doing it.

- Chris

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

On Tue, Mar 27, 2012 at 10:19:31AM -0400, Chris Lumens wrote:
> > Anaconda expects a minimum set of modules to be loaded, things
> > like raid1, etc.
> >
> > NOTE: Tested by appending to initrd of Beta RC2
>
> Yep, we did this back in the bad old days of loader. I guess we do need
> to keep doing it.

Out of curiosity, is there any reason the kernel couldn't just be building
those directly in to the kernel image these days? Seems silly to add this
thing to dracut to make sure we always load these modules. Just put them in
the kernel image if everyone needs them, right?

--
David Cantrell <dcantrell@redhat.com>
Supervisor, Installer Engineering Team
Red Hat, Inc. | Westford, MA | EST5EDT

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

David Cantrell (dcantrell@redhat.com) said:
> On Tue, Mar 27, 2012 at 10:19:31AM -0400, Chris Lumens wrote:
> > > Anaconda expects a minimum set of modules to be loaded, things
> > > like raid1, etc.
> > >
> > > NOTE: Tested by appending to initrd of Beta RC2
> >
> > Yep, we did this back in the bad old days of loader. I guess we do need
> > to keep doing it.
>
> Out of curiosity, is there any reason the kernel couldn't just be building
> those directly in to the kernel image these days? Seems silly to add this
> thing to dracut to make sure we always load these modules. Just put them in
> the kernel image if everyone needs them, right?

Does it need done in dracut? This could be done with a /lib/modules-load.d
systemd file (which would take effect on systems where anaconda is installed
at runtime, though.)

Bill

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

On Tue, Mar 27, 2012 at 02:49:49PM -0400, Bill Nottingham wrote:
> David Cantrell (dcantrell@redhat.com) said:
> > On Tue, Mar 27, 2012 at 10:19:31AM -0400, Chris Lumens wrote:
> > > > Anaconda expects a minimum set of modules to be loaded, things
> > > > like raid1, etc.
> > > >
> > > > NOTE: Tested by appending to initrd of Beta RC2
> > >
> > > Yep, we did this back in the bad old days of loader. I guess we do need
> > > to keep doing it.
> >
> > Out of curiosity, is there any reason the kernel couldn't just be building
> > those directly in to the kernel image these days? Seems silly to add this
> > thing to dracut to make sure we always load these modules. Just put them in
> > the kernel image if everyone needs them, right?
>
> Does it need done in dracut? This could be done with a /lib/modules-load.d
> systemd file (which would take effect on systems where anaconda is installed
> at runtime, though.)

dlehman has a plan to move some of these (things like raid) into
anaconda's storage module, but that won't happen for F17. We don't want
to build them all into the kernel since many users won't need them after
they install.

--
Brian C. Lane | Anaconda Team | IRC: bcl #anaconda | Port Orchard, WA (PST8PDT)
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

On Tue, 2012-03-27 at 14:49 -0400, Bill Nottingham wrote:
> David Cantrell (dcantrell@redhat.com) said:
> > On Tue, Mar 27, 2012 at 10:19:31AM -0400, Chris Lumens wrote:
> > > > Anaconda expects a minimum set of modules to be loaded, things
> > > > like raid1, etc.
> > > >
> > > > NOTE: Tested by appending to initrd of Beta RC2
> > >
> > > Yep, we did this back in the bad old days of loader. I guess we do need
> > > to keep doing it.
> >
> > Out of curiosity, is there any reason the kernel couldn't just be building
> > those directly in to the kernel image these days? Seems silly to add this
> > thing to dracut to make sure we always load these modules. Just put them in
> > the kernel image if everyone needs them, right?
>
> Does it need done in dracut? This could be done with a /lib/modules-load.d
> systemd file (which would take effect on systems where anaconda is installed
> at runtime, though.)

That's what I was thinking - we don't support using any of this stuff
(raid, dm crypt/multipath, etc) in initramfs anyway, so we could just
write out /etc/modules-load.d/anaconda-storage.conf in lorax.

I'm testing a patch to do that now and will send it shortly.

This anaconda/dracut patch is already in f17-branch, though. Reverting
patches is fun and all (also: whee! fewer files!) but I'm not gonna be
upset if we decide to leave this alone and load modules via conf file in
F18.

-w

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list