Skip to contentSkip to conversation

90kernel-modules-loaded must be --hostonly

DISCUSSION Warren Togami 2 participants 4 messages May 28, 2009 – May 29, 2009 3 messages not in the archive

lore
Share & tools
lore
#0 lore raw
Quoted 3 lines

/sbin/lsmod | while read mod rest; do
instmods "$mod"
done

This part relies on looking at the running system, and thus must not be part of the default dracut run. This seems OK for --hostonly mode.

Changing this will likely break some users depending on modules not otherwise pulled in elsewhere? Should I just go ahead and see what breaks?

Quoted 3 lines

[ -f /etc/modprobe.conf ] && dracut_install /etc/modprobe.conf dracut_install $(find /etc/modprobe.d/ -type f )

This part is fine.

Warren Togami
[email protected]
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw
Quoted 9 lines · Warren Togami
Quoted 3 lines

/sbin/lsmod | while read mod rest; do
instmods "$mod"
done

This part relies on looking at the running system, and thus must not be part of the default dracut run. This seems OK for --hostonly mode.

Changing this will likely break some users depending on modules not otherwise pulled in elsewhere? Should I just go ahead and see what breaks?

Oh, I now notice that the check script skips this entirely unless you are in hostonly mode. This is the reason why I'm not getting the KMS drivers loaded prior to plymouth (although plymouth itself is still busted for other reasons.)

[ "$1" != "-h" ] && exit 1

But is this correct? It seems we should be checking the hostonly variable and not if "-h" happens to be the first parameter.

-h isn't -H.
-h isn't --hostonly

Quoted 6 lines
Quoted 4 lines

[ -f /etc/modprobe.conf ] && dracut_install /etc/modprobe.conf dracut_install $(find /etc/modprobe.d/ -type f )

This part is fine.

Anyone disagree that this should be copied in all cases, not just hostonly?

Warren Togami
[email protected]
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): [email protected]

#4 lore raw
Quoted 22 lines · Warren Togami
Quoted 10 lines · Warren Togami
Quoted 3 lines

/sbin/lsmod | while read mod rest; do
instmods "$mod"
done

This part relies on looking at the running system, and thus must not be part of the default dracut run. This seems OK for --hostonly mode.

Changing this will likely break some users depending on modules not otherwise pulled in elsewhere? Should I just go ahead and see what breaks?

Oh, I now notice that the check script skips this entirely unless you are in hostonly mode. This is the reason why I'm not getting the KMS drivers loaded prior to plymouth (although plymouth itself is still busted for other reasons.)

[ "$1" != "-h" ] && exit 1

But is this correct? It seems we should be checking the hostonly variable and not if "-h" happens to be the first parameter.

Review

Quoted 2 lines
(quoted diff) +0 -2
-h isn't -H.
-h isn't --hostonly

This obviously broke by introducing the --help option.. just fix it. --
To unsubscribe from this list: send the line "unsubscribe initramfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): [email protected]

#6 lore raw
Quoted 20 lines · Harald Hoyer
Quoted 19 lines · Warren Togami
Quoted 10 lines · Warren Togami
Quoted 3 lines

/sbin/lsmod | while read mod rest; do
instmods "$mod"
done

This part relies on looking at the running system, and thus must not be part of the default dracut run. This seems OK for --hostonly mode.

Changing this will likely break some users depending on modules not otherwise pulled in elsewhere? Should I just go ahead and see what breaks?

Oh, I now notice that the check script skips this entirely unless you are in hostonly mode. This is the reason why I'm not getting the KMS drivers loaded prior to plymouth (although plymouth itself is still busted for other reasons.)

[ "$1" != "-h" ] && exit 1

Quoted 7 lines

Review

Quoted 5 lines

But is this correct? It seems we should be checking the hostonly variable and not if "-h" happens to be the first parameter.

(quoted diff) +0 -2
-h isn't -H.
-h isn't --hostonly

This obviously broke by introducing the --help option.. just fix it.

oops, no "check" is called with -h in dracut if $hostonly is set by "-H --hostonly" --
To unsubscribe from this list: send the line "unsubscribe initramfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html