> you do not think the current state of the patching > system in solaris > is just broken at the moment?
Never had a problem with it, because the management system I employ works completely differently. In my system, patches are never applied to production systems, but to the operating system build herself (I produce my own Flash(TM) builds based on Solaris 10). Once that build passes regression testing with the new patch, it is labeled as production release. This usually takes place at six month release cycles, although I do have automation in place to make it happen earlier, if the fix is critical. An upgrade, of possibly thousands of systems in parallel, if performed by a single click in the web browser of a custom software deployment server, and it'll bring the target nodes down, the network detects them and automatically reflashes them with the new OS build. There are no service interruptions at any point in this process, because the targets are nodes in clusters. I can't currently do these things with OpenSolaris; and it bothers me greatly. > I feel your pain though, and i mostly agree with what > you say. but i > think IPS can be improved to a point where it makes > my and your life > easier. The biggest pain with IPS right now is very poor and lacking documentation, and inability to run pre and postinstall scripts, instead of forcing the ABUSE of SMF. And no tools to build packages. Compounded, it just exacerbates the pain. -- This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list [email protected]
