On Sun, Jan 27, 2013 at 01:16:53PM +0200, Andriy Gapon wrote:
A> based on your suggestions and submissions I've produced the following patch:
A> http://people.freebsd.org/~avg/ng_ether-renaming.diff
A>
A> It's only compile-tested at the moment :)
A> but I'd like to get your opinion about the direc
Hello,
it looks good, for just interface renaming scope.
The problem of it is that you need to check if the ifnet pointer needs
updated as well.
For coming and going interfaces like vlans you would have to update some
pointers as well at least the ifnet one.
The complete patch would rather inclu
Guys,
based on your suggestions and submissions I've produced the following patch:
http://people.freebsd.org/~avg/ng_ether-renaming.diff
It's only compile-tested at the moment :)
but I'd like to get your opinion about the direction of the change(s).
I am going to really test the change very soon
face of interface renaming capability. Especially given that
>>>> interface
>>>> renaming and ng_ether _module_ loading may happen in an arbitrary order.
>>>>
>>>> I am not sure how to solve this best.
>>>>
>>>> One possibil
> >> renaming and ng_ether _module_ loading may happen in an arbitrary
> order.
> >>
> >> I am not sure how to solve this best.
> >>
> >> One possibility is to use if_dname+if_dunit combination for ng_ether
> naming. This
>
is best.
> >>
> >> One possibility is to use if_dname+if_dunit combination for ng_ether
> naming. This
> >> should be stable and available for querying. This behavior should also
> be
> >> backward compatible with ng_ether being compiled into kernel
> (if_dnam
of interface renaming capability. Especially given that
>> interface
>> renaming and ng_ether _module_ loading may happen in an arbitrary order.
>>
>> I am not sure how to solve this best.
>>
>> One possibility is to use if_dname+if_dunit combination for ng_e
happen in an arbitrary order.
I am not sure how to solve this best.
One possibility is to use if_dname+if_dunit combination for ng_ether naming.
This
should be stable and available for querying. This behavior should also be
backward compatible with ng_ether being compiled into kernel (if_dname
how to solve this best.
One possibility is to use if_dname+if_dunit combination for ng_ether naming.
This
should be stable and available for querying. This behavior should also be
backward compatible with ng_ether being compiled into kernel (if_dname+if_dunit
==
if_xname before any renaming
