Quoth Christine Tran on Fri, Oct 20, 2006 at 01:53:25PM -0400: > A customer thinks that being able to define your own milestone is a good > idea. The use-case is having a milestone called audit, boot to audit > and have all the tools for audit work and ro filesystems. This has been > asked before, and the answer was that it's not possible now, but would > the SMF team consider it for the future?
Can you explain what "audit work and ro filesystems" means? Does the user want to carry out some operations before the system has fully come up? I don't think we'll allow user define milestones per-se, but I think the Enhanced Profiles project ( http://opensolaris.org/os/project/smf-profiles ) may make it easier to do something similar. > Incidentally, if I were to > make my own dummy foo-milestone manifest and just drop it in > /var/svc/manifest/milestone, and modify some dependencies to make > multi-user-server its parent, would that do anything? I could try it, > but perhaps someone can save me 30 minutes? What do you mean by 'do anything'? > If I were to make a mistake a specify a dependency in two places (using > the 'dependent' and 'dependency' declaration in two manifests,) which > would take precedence? (if they are not identical declarations, that is.) I think whichever was imported second would fail, but I'm not sure. We've established a naming convention for dependents to avoid this, but unfortunately it's not enforced. > It's been discussed here that future Solaris patches which deliver new > versions of manifest will take into account customizations and preserve > the changes. How does it do that? If my modification involves the > exact thing that the new manifest wants to change, what happens? For > example, I used svccfg to change some property from X to Y. A patch > wants to change X to Z. Does this override my customization? Not if Y != X. On each import, svccfg stashes a pristine copy of the properties in the last-import snapshot, and on upgrade it uses it to determine whether you've customized any properties. For properties that you customized, it will refuse to change them. However, this means that there's no way to say "I want to customize this property to the same values," since svccfg will interpret that as uncustomized. David
