On 04/22/09 18:43, Erik Nordmark wrote:
[email protected] wrote:
>>>>
But then, if someone has created configuration on a non-existent
interface, and later the underlying datalink for that interface is
added to the system, how does one activate the latent configuration?
E.g., the net-physical script will need something like "ipadm
create-interface", or "ipadm init-intfprop <intf>" to create
the interface and apply the latent configuration.
>>> [email protected] wrote :
That is an implementation matter, right?
For dladm we solve it my keeping the properties for missing
interfaces in user space and some upcall to retrieve them when the
object comes into existence. One could do the same for these missing
objects, or one
But dladm doesn't allow you to create configuration for a missing
interface today, right (it only reapplies previously created config,
and the first creation requires the interfce to be present)?
Yes, but that doesn't change anything with respect to this issue. I can
create a property for bge3 while it exists, and then bge3 is missing. At
that point in time the system is in the same state as if I was allowed
to create the property for bge3 even if bge3 had never existed.
The system needs to deal with bge3 for the first case, and whatever that
implementation mechanism is, it can presumably handle the second case as
well.
Isn't the following two cases different:
(a) "link existed to begin with and went missing later on" and
(b) "link never existed to begin with"
In the first case, we already have an object before the link
disappeared. Since we have an object we could apply modify/delete
properties on it. So when it reappears the latest configuration will be
applied on it. In 'dladm' we could do it by making upcalls to the daemon
and in 'ipadm' we can do it by parsing the persistent store.
However in the second case, we don't even have an object to apply
modify/delete on it. Both these case need separate handling, right?
~Girish
_______________________________________________
networking-discuss mailing list
[email protected]
