rickey c weisner <rick.weisner at sun.com> wrote: > Since I write tools as a "hobby", if I need the data I am going > to use the kstat. > The flags basically mean >>> KSTAT_STABILITY_PRIVATE: Use at your own risk >>> KSTAT_STABILITY_VOLATILE: Use at your own risk >>> KSTAT_STABILITY_UNCOMITTED: Use at your own risk >>> KSTAT_STABILITY_COMITTED: Supported > So I guess it is sort of binary. > By labeling or documenting a kstat it may avoid a support call but > I forsee a rash of RFE's to get kstats marked KSTAT_STABILITY_COMITTED. > > So if put to a vote, I would follow a minimalist course, IF the one > with the least code change. I had rather generate/modify docs instead > or breaking/rewriting code. > > I really like the simplicity of the KSTAT_STABLE flag.
And it still meets my desire for a mechanism for evolution: if I really want to mark something as doomed, I could mark it unstable once more. Mind you, David J. Brown would probably hit me on the head with a large hammer, but we do thereby retain the capability of correcting an error. +1 --dave -- David Collier-Brown | Always do right. This will gratify Sun Microsystems, Toronto | some people and astonish the rest davecb at sun.com | -- Mark Twain cell: (647) 833-9377, home (416) 223-8968, bridge (877) 385-4099 code 506 9191#
