SunOS 5.8 Kernel Version will not update after patch was re-applied
I'm new to everything and have the slightest clue to where to begin...
I have a Sun V100 that is at kernel version: SunOS 5.8 Generic 117000-05, but is suppose to be at kernel version Sun OS 5.8 Generic 117350-34.
At one point the kernel version was updated to SunOS 5.8 Generic 117350-34. But after a patch bundle was re-applied which included the 117000-05 patch, the V100 rolled back to 117000-05 for the kernel version. Is there any way to get the kernel version back to 117350-34?
Thanks,
msUser24
[536 byte] By [
msUser24] at [2007-11-26 8:32:18]
# 1
Patching should refuse to overwrite a patch with an older patch.
How are you checking your kernel version.
uname -a is the easiest way.
Its possible that the file /etc/motd has a kernel version mentioned in the login message
whick is misleading you.
But that version could easily be out of touch with the actual kernel version.
# 2
Hi,You could check with "showrev -p" to see if the kernel version you want, 117350-34 shows up or not. Like Robert says it's not that easy to overwrite a newer patch with an older patch.... it shouldn't just do it like that.Regards,Nico
NicoB at 2007-7-6 21:56:10 >
# 3
One thing I have seen that can lead to problems of this kind.
If you have a mirrored root filesystem and one of the mirrors fails.
Then of course, the patched kernel isnt written onto the failed mirror.
But if you boot device is the failed mirror by default, you will boot up into the older kernel.
# 4
Yes, I agree with you all that the kernel version should not have changed. I used the command 'showrev -p' to view the kernel version and that's how I was able to determine that it changed back to 117000-05.
I will take the suggestions given and see what happens. The only other suggestion I was given was to re-install Solaris. What thoughts do you all have on that?
I appreciate the quick responses,
msUser24
# 7
Instructions for recent kernel patches require a boot -r.
On some of the Solaris 8 hosts I have patched recently, uname will not reflect the updated patch version until you do this. Some of the patched hosts seem to do a boot -r automatically at reboot (warning!)
Not sure why some hosts need it and some don't.
