On Fri, Mar 02, 2007 at 09:22:13PM +0800, Peter Memishian wrote: > > > > I think your second alternative is untenable, since it would mean > > > that a link name by itself (and thus an IP interface name by itself) > > > is no longer unique across the system, > > > > The meaning of a link name will always be context dependant, else how > > would a non-global zone be able to refer to "ip.tun0" and get to the > > right link? (That being "zone1/ip.tun0", or whatever naming is used > > to disambiguate). > > Sorry, I meant to say "zone", not "system". In the global zone, > "ip.tun0" would become ambiguous. That's the problem we'd like to > avoid.
I'm not sure about that, as it depends what operations we're talking about. The IP interface name is already disambiguated by the tools that manipulate such things, as they know that they have to find the IP stack that corresponds to the current zone (or the kernel code to which they talk does). Similarly, I'd like to be able to change properties of the link "ip.tun0" in the global zone and have it be implicit that I mean "global/ip.tun0", though perhaps this would be a detail of the implementation of dladm. dme.
