David Bustos ???: >Quoth Zhenghui Xie on Mon, Sep 25, 2006 at 03:06:45PM -0700: > > >>>The difference between boot & standalone is not a difference in network >>>environment, but a difference in knowledege about the network >>>environment. We always boot into the boot profile because we don't know >>>what the network environment is like at boot (because both the network >>>hardware isn't fully available, and NWAM is implemented in userland, >>>which isn't fully available). Once NWAM has started and done its >>>initial network probe, it has enough information to decide whether there >>>is a network or not, and if there's not, it can switch to the standalone >>>profile. >>> >>> >>But what if NWAM detect some network attachment one second later after >>the switch? how would this differentiation help us? >> >> > >It doesn't help in that case. There's nothing we can do for that. The >user will understand. > > > > >
This is exactly why I think we should disable this kind of service in the network profile. But not enable this kind of service in a *separate* standalone profile. If we have a bootup-profile, a separate standalone and some network profile, the service is disabled in bootup-profile, enabled in standalone profile and disabled in network profile. The sequence would be: boot up first using bootup-profile, service disabled => at some point(and this point is very hard to define), switch to standalone, service enabled => one second later, network detected, switch to network-profile, service disabled. If we just have one single bootup-and-standalone-profile, and some network profile, the service is enabled in bootup-and-standalone-profile and disabled in network profile. The sequence would be: bootup using bootup-and-standalone-profile, service enabled => at some point, detect network(this point is fairly easy to define), switch to network-profile, service disabled. If no network detected, service keep enabled. -Jan
