problems with MODULES_CONF_ALIAS_TYPE

[Jean-Christophe Dubois]

Matt,

On Friday 02 February 2007 05:58, Matt Domsch wrote:
> so yes, alias my_device comes before alias my_device0 which comes
> before alias my_device1.  It's doing the "+1" to make sure what it's
> adding is later than any previously existing entry (e.g. to not screw
> up your boot ordering by adding it at the beginning of the list thus
> loading the new driver before older drivers).

Thanks for you answer. I understand the reason for the +1 and the fact you 
don't want to screw up some ordering.

But here I "complain" about the fact that if there is no my_device string at 
all in the modprobe.conf file, DKMS will still add my "new" device as 
my_device1 instead of my_device0.

In my case my_device0 is a pseudo ethernet device and obviously I don't 
control the numbering. So the driver registers the pseudo ethernet device as 
my_device0. On FC5 I have a 
corresponding /etc/sysconfig/network-scripts/ifcfg-my_device0 file in which 
the referenced device is my_device0. So I would expect that when the kernel 
wants to bring up the my_device0 ethernet port, it will look for the module 
to load in /etc/modprobe.conf. And this is why my understanding is that I 
need the following line in this file:

alias my_device0 my_module

having

alias my_device1 my_module

does not help in my case.

So do you think it would make sense to modify DKMS so that it makes a 
difference between the fact that my_device0 is in the modprobe.conf file (in 
which case it seems OK to come up with my_device1 to be added to the file) or 
there is no my_deviceX at all in the file (in which case DKMS should come up 
with my_device0).

Maybe I am asking too much out of DKMS and I should come up with my own script 
to update modprobe.conf and all.

Regards

JC