Hardcode - major numbers

[Prashanth C]

Question about kernel major IDs for non standard drivers to ignite experts.

We have different releases of our product (on HP-UX 10.20). Each release also has an associated ignite image. We use make_sys_image to generate the ignite image.

In the ignite image for the older release, for two of the non-standard device drives, kernel major IDs had certain values.

In the ignite image for the newer release, the kernel IDs for these non-standard device drivers have changed. This might be because of certain new patches getting added (not sure)?

Question is:
1) Do the changed kernel IDs cause any problem (major problem or minor problem)? Will the system be stable with the changed kernel IDs?

2) Is there any way these kernel-IDs can be fixed while preparing an ignite image/tape so that while igniting a new server, they have the same kernel-IDs?

Answers and suggestions would be highly appreciated.

Thanks,
Prashanth

[Steven E. Protter · Accepted solution]

HP-UX kernels don't work that way. Its not like Linux.

They really are unique based on what patches were applied.

Try this:

what /stand/vmunix

on the various systems. You will see hundreds of revisions and patches.

The way Ignite works, is you build a base image of the Core OS.

Then you take a generic server with vanilla hardware and use make_sys_image to build a Golden image.

The Core OS is installed first, then the Golden Image witch patches, which can be substantially customized to deal with hardware concerns and different hostnames. You can even add post configuration logic to mirror or reconfigure disks after the image push.

With Ignite, the Kernel you end up with will be the one built into the Golden Image. There will be very few differences machine to machine.

If most machines have tape drives ond one doesn't then obviously the kernel won't come out with the stape driver built in.

Direct discussion of your questions:

Question is:
1) Do the changed kernel IDs cause any problem (major problem or minor problem)? Will the system be stable with the changed kernel IDs?

No. Ignite adjusts for that, though the 11.X products are better. 10.20 has no support any more, so this is the only place you can get help on that.

2) Is there any way these kernel-IDs can be fixed while preparing an ignite image/tape so that while igniting a new server, they have the same kernel-IDs?

You can prepare multiple golden images which can contain necessary kernel customizations.

Your configuration files will always go Core Os first, then the designated Golden Image. Judicous use of this feature should get you where you want to go.

Your biggest problem is 10.20 itself. It might be time to plan a migration if the hardware supports it.

SEP

[Prashanth C]

SEP, Thanks a lot for your reply.
We directly manufacture the golden image by the make_sys_image command. We do not prepare a core-OS.
You have mentioned that there is no problem if the major IDs are different. Can you please elaborate on this so that we can provide a proper explanation.
Since we are using only one command make_sys_image to produce the golden image, is there a way to hardcode the major numbers? Please let us know some pointers, or links to the above subject?
Sadly, we can not move to 11.x at this point.

Kind regards,
Prashanth