Tim Wright writes: > with /usr/sbin/patchadd linked to pdo, patchadd no longer seems to work with > a patch_order file i.e. > patchadd -M. patch_order doesn't install anything > patchadd -M. installs the patches in the current directory
For what it's worth, patchadd has known how to sort patches in dependency order since S10 FCS. There shouldn't be a need to generate or provide a "patch_order" file -- just give it the directory, and it'll figure things out. > This means that trying to add a patch cluster in a jumpstart profile: > > patch patch_order nfs://svr/path/to/patch/cluster > > doesn't work as it is effectively doing > patchadd -Mcluster_dir patch_order I'm not sure what the cause of the problem might be, but since you seem to be talking about OS patches, and there are no such things for any OpenSolaris-based release, it sounds like you're not using such a release, but are instead using one of the production releases of Solaris. If so, and if you do need explicit patch ordering, then you should get in touch with Sun's support group and file a bug. > Have got round this by linking patchadd back to the ksh script version ( in > the same dir as pdo ) Yikes! > but I assume this may cause issues if I want to jumpstart zones? I don't see how it could be supported. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
