Jason Ozolins writes: > Blastwave package upgrade == package remove followed by package install. Not > like, say, RPM's handing of upgrades at all. The service stops while the > upgrade happens. Not to mention, some of our config files got creamed (this > is really the packager's problem rather than inherent in SVR4 packages). > This kind of explains why Sun puts out _patches_ rather than new versions of > packages - because applying the latter can't be done easily to a running OS > instance. SVR4 package management just wasn't designed to work the way that > people expect package management to work these days.
Not true on both counts. A Solaris upgrade (as opposed to patches) uses packages. The difference is that the upgrade process uses SVr4 'admin' files when necessary. Blastwave could do this with "instance=overwrite," and probably should, but it doesn't. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
