On Wed, May 12, 2010 at 05:41:26PM -0700, Mark Haywood wrote: > Edward Pilatowicz wrote: > >On Wed, May 12, 2010 at 04:24:07PM -0700, Mark Haywood wrote: > >>Edward Pilatowicz wrote: > >>>some quick questions. > >>> > >>>how does this functionality interact with different network management > >>>services, specifically network/physical:nwam and > >>>network/physical:default? is network configuration only supported for > >>>one of these methods? if so, what happens if that method is disabled > >>>and another one is in use? > >>The new SMF services being proposed would run before > >>network/physical and would setup persistent configuration before > >>network/physical:nwam and network/physical:default run. So, this > >>functionality basically provides the system with an initial > >>configuration at first boot. network/physical:nwam and > >>network/physical:default should continue to function exactly like > >>they do today on *any* boot. That is, network/physical:default > >>continues to use the system persistent configuration and NWAM uses > >>its profiles to determine what to do. > > > >so it sounds like this new service will essentially configure the system > >to work with either network/physical:nwam or network/physical:default > >? > > Basically yes. This new service will not do anything to the NWAM. It > functions as it always has regardless of what the new service does. > As for network/physical:default, it will use the persistent > configuration provided by this network/install service at first > boot. > > >ie, the new network/install service will create/modify /etc/hostname > >file(s) so that if network/physical:default is enabled the system boots > >with the requested configuration, and, the new network/install service > >will also create and enable a static nwam profile so that if > >network/physical:nwam is enabled we'll get the same requested > >configuration applied? > > No. The new service runs ipadm to create a persistent configuration > (no /etc/hostname*.<intf> files in the future). This will be > consumed by network/physcial:default. NWAM ignores the ipadm > configurations and operates the way it always has. >
so it sounds like this new network/install service won't support systems using nwam. (since if nwam is enabled the system will not boot with the requested configuration.) so it seems like an error to have this service enabled and to also have NWAM enabled at the same time. also, i have the same question as tony. if nwam already supports profiles why is this case even needed? why doesn't install just apply a nwam profile to the system? ed _______________________________________________ opensolaris-arc mailing list [email protected]
