Quoth Zhenghui Xie on Wed, Oct 11, 2006 at 05:06:29PM -0700: > Above is the figure of service model, where an arrow shows a SMF dependency > and > each purple box represents a SMF service entity. NWAM will introduce a new > service ??network/profiled?? to SMF. This service will start NWAM daemon.
Why should NWAM depend on milestone/network? Shouldn't NWAM decide when to start milestone/network? I take it that you're going to keep network/loopback? Why? If the only reason is to know when to start milestone/network, then as I said above, NWAM should be doing that. > The definition of milestone/network (quote from Jim's email) will be: > - lo0 is configured > - configured IPsec rules, if any, are loaded > - configured IP Filter rules, if any are loaded Ok, but you should still obsolete it. ... > 3. ULPs > At boot up, the system will first apply information in the standalone ULP so > that services which can start early will be enabled right after NWAM daemon > starts. > > Meanwhile NWAM daemon will discover outside networks and try to connect to > some > network(s). If some network is connected, NWAM daemon may switch to some > other > ULP. The decision of switching will be made according to certain policies. > User > can explicitly specify that the system needs to remain as standalone, in which > case NWAM daemon won't switch to other ULPs. > > Below is the service list in the default standalone ULP. User can customize > this list in the default standalone ULP so that they can choose to > enable/disable services as needed. > > service name state in default standalone profile > ------------------------------------------------------------------- > milestone/single-user:default enabled This shouldn't be in any NWAM profiles. It should be enabled by default, and then if the user is dumb enough to try to disable it in one of his NWAM profiles, we'll either let him hang himself or warn him not to do that. > system/identity:node enabled but revisited* after online. > system/identity:domain enabled but revisited* after name service > * revisited means "refreshed if it changes" I'm not so sure these should be in profiles. I think they should be disabled by default and NWAM should be hardcoded to enable them (temporarily) once it has determined and set the node name(s) and domain name(s). ... > 5. Proposal for hostname: > Currently if the user wants to change the hostname of the system, s/he has to > either sys-unconfig then configure the system, or update a bunch of files then > reboot the machine. NWAM can introduce an interface for setting the hostname. > A > proposal to achieve this is: > * Use system/identity:node to keep track of system's hostname. > * When the user changes the hostname through the NWAM UI, NWAM will need to > update the node name in the kernel, update /etc/nodename and > /etc/inet/hosts, > and refresh system/identity:node. This should happen whenever the authoritative source of the hostname changes, not just through the NWAM user interface. Looks good otherwise. David
