Quoth Zhenghui Xie on Thu, Sep 21, 2006 at 05:29:30PM -0700: > >Not as you have presented it. I think your plan is to have the > >standalone profile active on boot. Then any services which the user has > >enabled in that profile will be started as soon as their dependencies > >are met. If a user wants the service to only be started once NWAM has > >verified that no networks are available, then NWAM will have to switch > >from the initial profile to a different standalone for this to happen. > > I don't think we have to switch to a different standalone. If a network > is available, we switch to a network profile, then user can just disable > those service(s) in the network profile(s). If no network available, we > will stay as standalone, and these services remain enabled, this is just > what the user wants. Right?
Usually, yes. Consider a user who has a service which should only run if there are no external interfaces, and which takes a long time to start up. If we boot into the only standalone profile, then we might start the service before NWAM has finished probing the network. If NWAM detects a network and switches to the networked profile, then the service will be disabled, but since it takes so long to start, it's still starting. In this case, the user will want the standalone profile to be separate from the boot profile, and he will want the service to be enabled in the former, but not the latter. Now if we can come up with a reasonable argument for why no one would ever want to do that, then we can ignore the scenario altogether. In lieu of that, though, it seems to me that we should keep it as a use case, however uncommon. David
