> True, I thought about this, but was worried about complicating the wording > to a point that it would become meaningless to the ley reader. I've > attempted to be more general in bullet 2 to address this. Let me know what > you think.
Looks good (considering a chipset as "topology" is pushing it, but I think for purposes of this article it's fine). > > * General comment: persistence isn't covered in the whitepaper. > > We should probably mention that (like other dladm subcommands) > > dladm rename-link will persist unless -t is used. > > Sure, I can mention that, but I don't want to give specific examples of > usage with -t. I don't want this to be the comprehensive documentation for > dladm, but rather a launching point for people to see what's possible and > what the benefits are. They can go from here to read the documentation and > complete their understanding. Agreed. > > Also, at > > least for example 1, we should mention that any files with the > > old names (such as the list mentioned in Example 2) would need > > to be located and updated. > > I understand what you're suggesting, but I'm not sure where the best place > to say this is in example 1. I've added a note at the end of the example, > is this what you had in mind? Yep. -- meem
