James Carlson wrote:
> I'm arguing that (a) there's no way to know whether we really have
> _sufficient_ external connectivity to allow any particular application
> to run correctly and (b) since we don't and can't know this, it
> doesn't make sense to have an SMF milestone that somehow represents
> this state.
I guess no one is disputing that connectivity can mean
different things to different network services. Jim's
point is that there is not even a meaning of "basic
connectivity" which is "meaningful." We can easily define
what "basic connectivity" means and make it the state
represented by milestone/network. Jim's contention is that
it is useless as it does not "guarantee" anything regarding
the "actual connectivity" of an app.
Now thinking of it, I probably asked the wrong question
about connectivity and milestone as I misunderstood the idea
of a milestone. Does reaching a milestone mean that it
is now guaranteed that certain operation can work? Or does
it simply mean that some services have started, but it does
not guarantee that those services work correctly? For
example, a name service, say NIS, has been started. But it
does not mean that it can return results as the NIS server
is not responding.
Could someone please explain what a milestone represents? I
tried finding out the exact meaning of a milestone, but I could
not find a precise meaning from the docs I checked.
--
K. Poon.
kacheong.poon at sun.com
