> It's much worse than that. The binary format of the > repository itself > is a project private interface. There's no guarantee > that it remains > compatible between patch levels, let alone between > releases. The only > guarantee given is that when it needs to change, the > system will > handle that change during the upgrade process. > > In other words, you can't safely use any of the tools > to manipulate > the state of a separate image of Solaris. That's why > actions taken > during upgrade that must manipulate the repository > are postponed until > after reboot.
Great; didn't I just walk into a mine field on that one? I guess I'll have to split my work in two phases, since I've already lost 15 16-hour days on the entire DNS solution. The first phase will be to implement David's suggestions. The second phase will be constructing a special one-time manifest that adds our instance of dns/server, then deletes himself after that. I have to split this up, or else I won't be done with this until next year... I keep hitting these recursive dependencies... This message posted from opensolaris.org
