https://bugzilla.novell.com/show_bug.cgi?id=343856#c1 Michal Marek changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |agruen@novell.com --- Comment #1 from Michal Marek 2007-11-27 13:44:21 MST --- When there are multiple modules that match an alias, all of them are inserted, in the order they appear in modules.alias. Due to the linked list juggling in depmod, the modules in (weak-)updates/ currently come last (fixable). However, when modprobe runs, it's hard to tell from looking at modules.alias which modules should override what (to do it right, it would have to parse depmod.conf as depmod does). And statically determining in depmod which aliases overlap (and how) and generating a modules.alias that does the "right thing" is hard as well. I'd suggest that if a kmp wants to override a module with a different name, it should just drop a file in /etc/modprobe.d with blacklist oldmodule or alias pci:..... newmodule if newmodule should only win for some ids (modules.alias is only consulted if there's no matching alias in modprobe config). Is that ok with both of you? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=343856 User mmarek@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=343856#c3 Michal Marek changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mmarek@novell.com Status|NEW |NEEDINFO Info Provider| |agruen@novell.com --- Comment #3 from Michal Marek 2008-03-20 04:31:06 MST --- (In reply to comment #2 from Andreas Gruenbacher)

It seems we are misunderstandinghere. Let me try with an example -- in /lib/modules/$krel, we have:

kernel/foo.ko alias: bar alias: baz updates/foo.ko alias: baz

In other words, updates/foo.ko overrides kernel/foo.ko. modules.alias will only refer to updates/foo.ko; the other module won't show up there anymore.

A ``modprobe foo'' will load updates/foo.ko. A ``modprobe baz'' should do the same. But what does a ``modprobe bar'' do? AFAICT it should fail -- does it do that, or does it load kernel/foo.ko instead?

'modprobe bar will' fail (just tried it) -- updates/ completely overrides modules of the same name in kernel/, so the 'bar' alias won't be written out to modules.alias. Is this what this bugreport is about? If so, it can be closed, because there's nothing to fix. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.