David> By default policy, I presume you mean that the user has declined to David> express what should be done when certain networks are encountered. David> In effect, the user either skipped that part of the install, or he David> JumpStarted with no explicit network configuration.
Yes, a scenario more or less like that. David> ... what's the use case? I gather it's the data center ... Primarily but not exclusively. David> ... which is presumably using JumpStart. We'd like to think that, but there's also the "I just got this big box and plugged it in; let's boot it up" scenario. David> If so, what services are we supposed to offer? Just ssh? Wouldn't David> that require the user to log in and configure what services to offer? I'm not following: if JumpStart is used, then we do whatever the profile says; otherwise, we do whatever the Solaris default is. David> Wouldn't it be better to just require that the user configure the David> network during the JumpStart? It might well make our life easier, but per above, I'm not sure if we can require that. David> I'd think that we should decline to participate in any wireless David> networks unless directed to do so by the user... Sorry for not providing context earlier, but I completely agree. There is another design thread, which I expect to be published here very soon, which makes this clear. David> Note that I think concepts like plumbing are really implementation David> details that should not be allowed to muddy the user experience David> scenarios. I think I agree, but I don't see your point, so I'm not sure. -- John http://blogs.sun.com/jbeck
