My guesses
One of the servers didn't reboot ? The uname -v just shows the kernel
patch level, so it indicates that the kernal patch hasn't applied (or
taken effect)
Try just running "showrev" to check out what kernel patch is applied to
each.
Solaris wrote:
Hello all,
I've got a jumpstart server that recently jumpstarted 3 separate,
brand new Sun Fire V210 systems. All three used the same jumpstart
profile, which installed the same version of Solaris 8, the same OS
install level (SUNWcall), partitioned the disks the same and all three
called the same finish script. In that finish script I automatically
install the Feb 2005 recommended patch cluster. When these V210s were
finished jumpstarting and they rebooted after the patch cluster
install, I looked at their kernel patch versions with "uname -v", and
2 are the same version and 1 is not. It is imperative that these be
the same as they are getting shipped to customers. A few questions:
-Any idea why these "uname -v" values would be different?
-Any idea how to tell what cluster patch the OS thinks is installed? I
don't think there is an equivalent, but something similar to
/etc/release, but for the patch cluster.
-Any way to insure 2 systems are at the same patch level without
having to do a manual comparison of a showrev -p output?
-Could the "uname -v" be different if there was a hidden hardware
difference such as a motherboard rev?
It seems the cluster patch area is a bit of a mystery on Solaris any
hints on how to ensure 2 systems are the same from a patching
perspective, would be greatly appreciated.
Thanks in advance and happy holidays.
-Mark
_______________________________________________
Solaris-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/solaris-users
_______________________________________________
Solaris-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/solaris-users