Re: [Madwifi-devel] [PATCH] variable interface name prefix
Status: Beta
Brought to you by:
otaku
From: Michael R. <ma...@no...> - 2004-05-26 15:22:10
|
Hi. Dmitry A. Fedorov wrote: >>So I understand that you propose to have a "local" moduleparm.h, that >>either includes the "linux" version or resembles its content for kernel >>versions that do not have their own. Is that correct? > Just copy moduleparm.h from 2.4.25 kernel to madwifi/include/linux, > the madwifi/include/ dir is in the headers search path already. I'll give it a try. >>Do you have some examples? One that would come to my mind would be the >>sysctl interface, > yes >>but I don't think it would make sense to adjust these >>names. > but without it this name change mechanism will be incomplete. As far as dynamic sysctl controls are concerned (as those introduced by the link distance patch I posted earlier today), they will automatically follow the naming of the actual interface. That is, if you ifname="atheros", you will find the "distance"-setting for the first interface at dev.atheros0.distance. If the static (global) sysctl controls would be changed to follow the naming, too, you would end up with things like dev.atheros.debug. Even worse, if you use ifname="eth", you will have dev.eth.debug, which could be totally confusing. For this reason I think that the global sysctl controls should retain "ath" in their name. But I won't defend this with my life, so if there are good reasons, bring them on :) Bye, Mike |