New install of 10.20

[Jenifer Martins]

I am currently installing 10.20 (April 1999 version). We need to use 10.20 because our other applications are not compatible with 11.0. Along with the April 1999 Core OS CD, came the Support Plus CD (June 2001). There are several bundles listed...one for General Release XS800GR1020 and the other for Hardware enablement/critial patches XS800HWCR1020. Are these important to install?

This is a 9000 Dclass File Server. I will eventually connect the DLT8000 Autoloader and an External SureStore Unit. This system will be "validated" becauseof GMP regulations... that is why I need to know this stuff. Any information will be helpful.
Thanks.

[nancy rippey]

The bundles should be installed. The General Release bundle will include security patches along with any Y2K patches, since you are installing from April 99 you would want these.

[Sanjay_6]

I believe thje HWCR Bundle should be a must. You may want to load the General Release patch bundle too as it contain new patches which have superceded the patches you haev on april 1999 CD.

Thanks
Sanjay

[James R. Ferguson · Accepted solution]

Hi Jenifer:

The General Release (GR) bundle is a superset of the Hardware/Critical (HWCR) bundle. Install the GR bundle for the broadest patches.

If you examine the actual patches in each bundle, you will see that the HWCR bundle is a very, very close subset of the GR one. In some cases, slightly earlier or slightly later versions of a particular patch stream can be found depending on when the bundle, at large, was certified.

My preference is always the GR bundle.

Regards!

...JRF...

[Bernie Vande Griend]

Jim is correct. I would also add the Diagnostic software from that same support CD. It will come in handy with finding and resolving hardware issues.

[David Lieberman_1]

Hi Jenifer,

Do you have access to the Custom Patch Manager (CPM) on the ITRC?

I prefer CPM over installing CD bundles because a patch analysis (on HP's ITRC server) is performed for the target server, as well as a display (and selection) of the latest and recommended patches for that server.

If done correctly, the result is a customized patch bundle that can be downloaded from the ITRC. This bundle should satisfy your patching needs without the "bloat" of many extraneous patches included in the HW and GR bundles, reducing unnecessary filesystem usage.

If you must install from CD, I'd select the GR bundle if you only want one bundle installed. It won't hurt to install both as many patches are (more or less) duplicated.

HTH
David Lieberman

[Jenifer Martins]

Since I am will to take the risk, I installed the XSW800GR1020 bundle. It took several hours, but no errors until reboot. I am currently getting the "INIT: Command is Respawning too rapidly. Will try again in 5 minutes." But there are not errors in /usr/vue/bin. I don't know that this is.

Also, How do I connect to hp.com via HP-UX. I am not familiar with downloading patches, and unix files from the internet to my hp server.

[James R. Ferguson]

Hi Jenifer:

The "init spawning too rapidly" syndrome can be nasty to isolate. Consider carefully *everything* that you have done between the time you last successfully booted your system and its current condition. I recognize from your post that it would appear that the problem began immediately after applying (only?) patches.

Take a look at the following two documents from the Technical Knowledge Base: #UXDNKBRC00000918 and #KBRC00000740. They give you the steps you need to follow to isolate the problem's cause.

Take a look at /etc/rc.log for warnings and errors in startup scripts. Look at /var/adm/syslog/syslog.log for the full message(s) from 'init'. There may be more information than what you have posted.

...JRF...

[Bill Hassell]

The INIT respawning error is limited just to those items in /etc/inittab, the most common is a getty running on an unconnected MUX or RS-232 serial port. If you aren't using any serial ports (except console), change the word respawn to off. Look at all of the lines with the word respawn and make sure all of them are off (except console!) and any you know are connected correctly.

[Wodisch]

Hello Jenifer,

you can see the "exit" and "termination"
codes of the commands executes from within
"/etc/inittab" by entering "who -a".
The ones having codes other than "0" (zero)
are the candidates to cause your problem and
are those to be investigated further.

HTH,
Wodisch