> Oh. Yes, that does sound like a pretty serious constraint. The main > problem you'll likely run into is that it can be hard to keep up with > packaging changes -- if one of those packages suddenly grows a new > dependency or changes name, you could find yourself debugging your > software configuration. > True, but one can also hope that Xvm and its dependencies will stabalize some day (glass half full)
> Under the covers it runs pfinstall(1M) to do the work, and that > documents what happens. > The man page for pfinstall(1M) does a good job explaining how to use pfinstall, but its not clear in explaining what "testing a profile" means... > You should probably also check out this tool: > > http://www.opensolaris.org/os/project/svr4_packaging/package_companion/ > > Ahhh, this tool will be very handy! - thanks for the link! > And this document: > > http://www.opensolaris.org/os/community/security/files/minimization-support-rules-ext.pdf > According to this document, my installation would be unsupported - not because I add pacakges, but because I don't install on the dependencies when I do. For instance, the Java runtime depends on XWindows and since my server is headless (console-access only), I skip it... All this put together, I think that I might have to skip Live Upgrade altogether and do it on my own using the following strategy: 1. do a fresh install of latest SUNWcreq into a DomU 2. pkgadd Xvm, python, etc. and configure as needed 3. copy result onto a spare compact flash 4. reboot system using new CF Of course, I'd rather not, but what other option I have? Thanks, Kent
