Sebastien Roy wrote:
> Section 5.1.1
>
> * There may need to be some initial step here when NWAM comes into being.
We need to think about this. For example, after NWAM, those
/etc/hostname.xx files will go away. So the method mentioned
in the doc is no longer valid.
> The fact that NWAM will automatically plumb IP on every available physical
> data-link by default will mean that the administrator will somehow need to
> tell NWAM to keep away from the data-link while it's being renamed. I'm
> not sure how this is going to work.
So an admin decides to use the CLI to rename a name. Will there
be some form of notification? If not, NWAM will not know about
this name change and funny thing can happen in the mean time.
> This is also kind of awkward since
> NWAM is scheduled to deliver after UV, so I'm not sure what the plan is
> for this kind of documentation.
We have on and off discussed about how NWAM will interact with
manual changes done not using the NWAM provided tools. If an
admin uses the NWAM provided tools, everything will be fine. One
crude way to solve this is to have NWAM modified "all" those network
configuration tools such that NWAM will be notified when a manual
change is done using those tools. I guess this should probably
be the last thing we should consider doing. Suggestions?
--
K. Poon.
[EMAIL PROTECTED]
_______________________________________________
networking-discuss mailing list
[email protected]
