Hi Seb, As a context for the second example (Replacing a NIC), you give a system that has bge0 which, upon installation, was renamed mgmt0.
For clarity, I suggest to add explicitly that one of the givens in this context is also that other network and application configurations on the bge0 interface, such as those on the preceding bulleted list, refer to that interface using the name mgmt0. This will highlight better the conclusion showing how a single rename-link operation spared the administrator from reconfiguring those network-aware services and applications - because they were already configured for mgmt0 to begin with. Thanks, Raoul Sebastien Roy wrote: > Folks, > > Here's my first cut at the UV whitepaper for BigAdmin. I'd appreciate > some critical eyes and comments. > > http://www.opensolaris.org/os/project/clearview/uv/howto/ > > It's not meant to be the UV documentation, Raoul has already done a > great job with that. Rather it's a demonstration of the benefits of > giving meaningful names to network datalinks using three concrete > examples. I stole one of the examples from my blog, but since it's > mine, I didn't see a problem with that. ;-) > > -Seb > > _________________________________ > clearview-discuss mailing list > clearview-discuss at opensolaris.org
