>> What does the project team, and what does ARC think, about just yanking
>> these interfaces in Nevada, and marking them Obsolete in S10u5?
>>
>> Are we willing to deal with the fallout from the breakage from the places
>> that have done their own thing? IMO, this breakage is not very different
>> from the precedent set by SMF... when SMF came out, a bunch of
>> administrative practice surrounding init.d scripts and inetd.conf was
>> "busted". I think folks adapted rather gracefully to it. Furthermore, I
>> think the scope of breakage that would be created by removing the NDD
>> command and underlying ioctls (at least for NIC drivers) is not too bad.
>> Indeed, not every NIC driver even supports these ioctls.
>>
>
> While this is all true, I disagree that we should break these interfaces
> in S10u5 - we can mark them Obsolete and provide legacy support for the
> ndd paths.
>
I think that's what I said... mark them obsolete in S10u5, and maybe
remove them in Nevada.
-- Garrett
