I've installed the latest recommended patch cluster for Solaris 10 on a
U60 and observed a number of retun codes =1.
Is there a major problem here?
Stuart
Is there a major problem here?
Stuart
> Is there a major problem here?
> Stuart
For now.
Looking at the logs I found a few messages to the effect that the
architecture for a certain package differs from the package installed
on the system....
Now.. I know I didn't install x86 patches on the U60... :-)
Stuart
Architecture for package SUNWcakr from directory SUNWcakr.v in patch
121236-01 differs from the package installed on the system.
The architecture it talks about is the kernel architecture (arch -k).
The patch is for sun4v (niagara machines ?) only, while your U60 has
sun4u architecture. So it actually means that the patch is for a
packages which is not installed on your machine, and therefore can
safely be ignored.
mp.
--
Systems Administrator | Institute of Scientific Computing | Univ. of Vienna
> It's probably patches like 121236-01 that showed this message:
> Architecture for package SUNWcakr from directory SUNWcakr.v in patch
> 121236-01 differs from the package installed on the system.
> The architecture it talks about is the kernel architecture (arch -k).
> The patch is for sun4v (niagara machines ?) only, while your U60 has
> sun4u architecture. So it actually means that the patch is for a
> packages which is not installed on your machine, and therefore can
> safely be ignored.
That makes sense; I guess I was expecting that would yeild a different
return code than "1"
Stuart
The patchadd man page documents a new option:
-t
Maintains the patchadd return codes from the Solaris
release prior to Solaris 10. On a system with zones(5)
installed, a return code of 0 indicates success. Any
other return code indicates failure.
This results in:
# patchadd -t 121236-01
Transition old-style patching.
Checking installed patches...
Patchadd is terminating.
# echo $?
8
return code 8 is "Attempting to patch a package that is not installed",
which makes more sense. On the other hand, patchadd -t doesn't show a
verbose error message on why it terminated.
Maybe someone can fill us in on why this changes happened.
mp.
--
Systems Administrator | Institute of Scientific Computing | Univ. of Vienna
1. Recommended patch cluster - patch not applied
Hi,
How is it possible to find out which individual patches have not been
applied and the reason(s) during a recommended patch cluster on Solaris 9 ?
Thanks in advance
2. Windows tries to read Linux drive -- Help!
3. disk perf: multiple mode IDE-patches + cluster patches ?
4. Can't start X, I/O error in /dev/console
5. Install a patch "cluster", can I removed older version of patches?
7. Sol10: patching with local zones
8. Enlightenment stole my processor!
9. What is your patch strategy on Sol10 ?
10. Solaris 2.5.1 y2000 Patch Cluster dependency problem
11. Problems with the latest Patch Cluster for Solaris 8
12. Problem with solaris cluster patches
13. Solaris boot problem after applying cluster patches