On 3/18/2009 at 11:30, Michal Marek
wrote: Dominique Leuenberger napsal(a): the vmware KMPs install a /etc/modprobe.d/vmnics file. I will change this to the new file name with the next monthly sync with upstream. I think I sent you a submitreq already.
Ok.. I think the SR went against the -devel project of those packages, which lies in Pavol's home. Thanks for that. I'm sure Pavol is going to propagate it in this case.
I was though wondering what importance / function the number 50 has. I assume it is sort of priorization? Can you elaborate on this please?
It's just a number between 00-system.conf and 99-local.conf, it doesn't have to be exactly 50 if you don't like it, but you should use a two-digit prefix to that the files are read in a sensible order.
Thanks for the explanation... so having 50 as the 'distributor' standard does not sound to wrong. I just go with the flow here ;)
$name: should this be in any way related to the package name? so far, the vmware-kmp installs a file called vmnics (as it mangles the loading of vmnics (virtual machine nics). Should that also be adjusted to reflect any given name?
That's really up to you. If you want to change the name to something better then it's a good idea to do it now as you have to rename the file anyway, but I don't think there need to be rules for it.
Define 'better' :) the file is called to what it does and serves on. Having the file called in some sort of related to the package it comes from could avoid possible clashes (granted, the amount of modprobe.d/*.conf file is rather small, so it should not happen anyhow). Dominique -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org