Peter Memishian wrote: > > Yes. That is a problem. > > > > But I am thinking of this problem for a while: currently we proppse to > make > > the datalink configuration API (the APIs to manage and persist datalink > > configuration) to be part of libdladm. Then all other libraries will have > to > > depend on libdladm. But at the same time, as it is currently true, > libdladm > > depends on other libraries too. > > > > I think we have to introduce another library to hold all the common > functions. > > Or use a registration mechanism and function pointers. > I thought about this, but I am not sure how this is going to work. Specifically, when the registration is done and who initiate the registration?
Maybe I am missing something. Thanks - Cathy
