David> The second draft of the Enhanced SMF Profiles design is now available
David> at http://opensolaris.org/os/project/smf-profiles/Design ...
1.1.1
* Why does a manifest get re-imported at boot even after an explicit
`svccfg import`?
* What do you mean "Properties ... can have any number of values ..."?
1.1.2
"Only SMF-initiated snapshots are available today;" is this true? I.e.,
is the interface really completely internal or merely project private?
2.1.1
A lot of this sounds good, but is written at a very theoretical level.
Specific examples would make it much easier to understand. I noticed
this particularly in the Multi-Package Profiles section, though it
applies to others.
2.1.2
In the Conditional Profile Order section, this text:
this project will provide a mechanism for condition developers
to declare mutual exclusivity, and it could deliver functionality
to determine when predicates might coincide. User interfaces
would use the latter to preemptively detect when profile
conditions are ambiguous and guide the user to a resolution.
This project won't deliver any such sophisticated user interfaces,
however, so we will leave implementation of ambiguity-detection
functionality for a future project. (See future work item
"Ambiguous conditional configuration detection.")
is confusing, particularly the "will" vs "could" in the first sentence.
If I understand the meaning correctly, it would be better to end the
first sentence (and paragraph) after "exclusivity", then start a new
sentence (and paragraph) to express the "maybe in the future" topics.
2.2.2
* Note: libwladm has been subsumed by libdladm.
* Please s/interface/network interface/ where appropriate for clarity.
2.2.6
Why did you list ns_nis in admin instead of ns_dns as SXDE seems to do now?
2.3.4
* I don't follow the first bullet under "Incompatibilities".
* nit: s/who's/whose/
2.3.9
Again, examples would really help clarify this, especially in the "Service
implementation" section.
2.5
* Condition Strings: modulo stated caveats, this sounds like a Good Idea
* Sophisticated Condition Constraints: not sure of details, but something
like this should be supported
* Modification Interfaces: probably; Solaris in general has too much cruft
* Runlevels, NWAM, and the service level profiles
* multi-user-server does seem to be multi-user + a bunch of net services,
but there are other net services which multi-user-server does not
depend on.
* multi-user depends mostly on local services, but it does depend on some
net services as well.
-- John
http://blogs.sun.com/jbeck
