Richard L. Hamilton wrote: > How about this approach, only to be used for services where the pre-existing > config file format was (give or take the odd Solaris extension) > cross-platform: > > add "import-native" and "export-native" to svccfg, which would require > a skeletal manifest to first be imported, that identified a plugin which would > digest an externally defined config file format, the location of the config > file, and also contained any other properties that could not be derived from > the config file. Conceptually and for the purposes of the "archive" and > "export" subcommands and the like, the result of applying the > "import-native" command would be a complete > manifest derived from the merging of the skeletal manifest and the native > format config file.
More stuff! People are confused enough between the snapshots, which props are in service and which props are in instance. I don't think they can take more modularity. Apache has a million little tweaks. It's all in httpd.conf and SMF doesn't care. I want it all in one place but I want that one place to be accessible and the language for me to get and put things into that place to be simple and clear. CT
