Peter Memishian writes:
>
> > There are a host of interaction issues to deal with here. Zones
> > currently causes arbitrary interface names ("addif") to be used, so
> > you wouldn't be able to use this feature in non-global zones, at least
> > until Clearview's vanity naming arrives. (And then you'd have the
> > issue of how interface renames ought to be handled ... does dladm know
> > about this usage, or does the system just fall apart when you rename
> > things?)
>
> I haven't followed this whole thread, but to be clear: you cannot rename
> a link that's in-use (e.g., plumbed).
Of course. But taking it down, renaming, and bringing back up is just
as harmful.
The issue I'm pointing out is that the interface names already have
complicated relationships to the configuration files, and adding a new
way to have a relationship is yet more complication.
I know that the dladm rename model is that things within dladm remain
consistent under rename, but that you just have to know what you're
doing outside of dladm. I don't disagree with that model, as it's
obviously the most flexible.
If there are, though, useful ways to avoid creating new things that
may break under a purely "vanity" renaming, and thus avoid service
calls, that might be good.
--
James Carlson, KISS Network <[EMAIL PROTECTED]>
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
_______________________________________________
networking-discuss mailing list
[email protected]
