size of /usr vs adding patch bundles

[David DiBiase]

we just recvieved new 4440. FS sizes, I guess are default. I ran swainv because loading Oracle and othe apps require the latest GoldPak and other patches be on the system. /usr never has enough space so I waste a lot of time rebuilding 'stuff'.

What am I missing here. Should I just rebuild every system that comes in??

[Patrick Wallek · Accepted solution]

Yes. That is my standard operating procedure.

That gives me absolute control over what is installed, what the filesystem sizes are, how things are set up, etc. That way I know that the system is set up EXACTLY how I want it.

Reinstalling the OS, adding the HP-UX apps needed, patching fully and adding whatever personal / corporate tools are required, may take a couple of days, but it is well worth the time.

[Steven E. Protter]

Shalom David,

Yes, every system should be rebuilt. Do you really trust the sizes and software picked by someone who does not know your businesss?

SEP

[sajeer_2]

Hi David,
It is better to rebuild the new system.It is the general practice.If you have lots of new systems,you can make a golden image using ignite-ux and use that image to install other servers.

sajeer

[Bill Hassell]

The preinstalled software layout is never correct. For a very small workstation, the disk layout may waste space but for something extensinve like Oracle or Sybase, etc, the sizes are far too small. It's important to be quite generous with /usr /opt and /var. So plan on rebuilding each server.

[DCE]

In my opinion, The LV sizes from HP are totally inadequate. They weredesigned for smaller disk sizes, and bear no meaning for the disks that are now available.

Definitely rebuild the system - either do a cols install or make an ignite tape, and do an interactive ignite restore to change the LV sizes

The ignite option is nice in that you do not have to reapply patches or reinstall purchased HP software

[James R. Ferguson]

Hi David:

Yes, resoundly, absolutely rebuild your system. I find that factory ignited systems have woefully undersized filesystems, not only for '/usr', but '/opt' as well as '/var' and '/tmp'. Personally, I like a generous '/tmp' and '/var' for the ability to stage patches and download optional software.

Moreover, I have noted, that the patches provided during factory installation are not necessarily complete.

Begin with the OE (Operating Environment) CD/DVD set that you licensed; add any individually licensed Applications not licensed with your OE; apply the *latest* SupportPlus or Standard Patch Bundles from the ITRC patch database; and follow with the current Online Diagnostics (Support Tools, EMS) bundle.

You can get the latest patches here:

http://www1.itrc.hp.com/service/patch/releaseIndexPage.do?BC=main|

...and the Online Diagnostics here:

http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=B6191AAE

You may also wish to add optional software from:

http://www.software.hp.com

Regards!

...JRF...

[David DiBiase]

Thanks for confirming what I usually do. I am constantly running short of time these days and chose a factory ignited machine.

I had hoped that HP had finally corrected their brain-damaged FS ignite specs. I don't want them to anticipate my application needs, just the minimum requirements to install their own recomended patch bundles.