SUMMARY: TruCluster nodes reporting different software releases

From: Martin Barrett <martin.barrett_at_carltontv.co.uk>
Date: Wed, 10 Oct 2001 15:15:47 +0100

I was wondering why uname gave a different version on node 2 of our cluster.
It was giving version P5.1 release 388.
Thanks as ever to Dr. Thomas.Blinn_at_Compaq.com for an amazingly prompt response.
Tom suggested that we were not running the correct Kernel.
He was of course correct.
His reply was very informative so I repeat it here.
...................

There is no place you will find the details.

If you go examine the kernel build files that are being used on the
second member, you should be able to figure out that the string "P5.1"
is being constructed by the newvers.sh file in the /sys/conf area,
and that the "P" is probably coming out of the "version.type" file
in that same directory.

For a released product kit, the version.type file is SUPPOSED to have
a "V" in it. But sometimes it's got a "P" if there are patches, and
I believe that the patch releases that deliver a genvmunix put a "P"
in the built kernel.

So I've got to wonder why you are running a kernel that has a "P" in
the string that was contructed when it was built. It's possible that
the cluster generic kernel has a "P" in its name string, and you are
not yet running a target kernel on that platform. Or it's possible
that somehow the "V" in the file got changed to a "P", although I can
not imagine why that would happen.

You ask "does this matter?". Not really, as long as the kernel works
correctly. It's just data being displayed, and it's data that you
can change to your heart's content by playing with the files found
in /sys/conf.

To get ALL of the kernels to output the same string, you need to be
sure that each was built using the same inputs to newvers.sh (which
creates the version.c file that's supposed to get built into each
kernel to reflect the kernel version data). And since the files are
shared by all the kernel build environments, they SHOULD all pick up
the same data; so it's unclear to me why one kernel doesn't, I'd be
looked at the vmunix file for that system, I bet it's NOT the target
or custom kernel that should have been built.

Tom
 
 Dr. Thomas P. Blinn + UNIX Software Group + Compaq Computer Corporation
  110 Spit Brook Road, MS ZKO3-2/W17 Nashua, New Hampshire 03062-2698
   Technology Partnership Engineering Phone: (603) 884-0646
    Internet: tpb_at_zk3.dec.com - or - thomas.blinn_at_compaq.com
     ACM Member: tpblinn_at_acm.org PC_at_Home: tom_at_felines.mv.net

  Worry kills more people than work because more people worry than work.
Received on Wed Oct 10 2001 - 14:16:42 NZDT

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:42 NZDT