The original post is shown below. Several people asked if I had
rebooted the machine after applying the kernel patch - the answer
is yes. In fact, I did a reconfiguration reboot, just in case it
Since the machine had only recently been installed, I persuaded the
owner to re-install the OS, since I had some doubts about the integrity
of the original install. This did solve the uname problem I originally
reported, so the problem is somewhat moot at this point.
Casper Dik did suggest using the strings command to search the kernel
file: strings /platform/sun4u/kernel/sparcv9/unix | grep Generic
strings /platform/sun4u/kernel/unix | grep Generic
as another way of confirming the kernel version.
I recently assisted someone with a Solaris 7 installation, and I
noticed something unusual. After applying the latest kernel patch
(106541-10), the command "uname -a" still shows:
SunOS jackson 5.7 Generic_106541-02 sun4u sparc SUNW,Ultra-5_10
although command "showrev -p" shows revision 10 as being applied,
and no errors appeared when I applied the patch.
In Solaris 2.5.1 and 2.6, the "uname -a" command shows the current (i.e.,
latest) revision of the kernel patch.
I'm not sure where the uname command retrieves this information,
and why it is not displayed correctly. Is this a symptom of a file
being corrupted, or is it related to whether the machine is booted
in 32- or 64-bit mode? (The machine is in 64-bit mode).
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:14:06 CDT