topic Re: Registering plain executables in SAM in Operating System - HP-UX

Registering plain executables in SAM

GBR — Tue, 25 Jul 2006 08:52:49 GMT

I grabbed a bzip2 executable from Merijn's HP-UX software site, and it seems to be working fine. Is there a way to register the software in SAM, so others will know bzip2 is sitting on the box?

Re: Registering plain executables in SAM

melvyn burnard — Tue, 25 Jul 2006 09:04:11 GMT

there used to be a way of adding in your own functions to SAM, but as SAm is being obsoleted, tthis may not be available anymore

man sam
then look for the section entitled:
Adding New Functionality to SAM

Re: Registering plain executables in SAM

A. Clay Stephenson — Tue, 25 Jul 2006 09:05:07 GMT

Whatever "registering" is, SAM doesn't do it. HP's approach is Software Distributor which includes swinstall, swremove, swcopy et al. These can be invoked by SAM although they are more commonly invoked directly from the shell. In any event, unless the software was swpackage'ed into a depot then it will not be installed in the Installed Software Database. Software from HP as well as from any of the HP-UX Porting Centre's is distributed as an SD bundle but other software (e.g. Oracle) is not and your box won't have a clue that Oracle is installed.

Re: Registering plain executables in SAM

James R. Ferguson — Tue, 25 Jul 2006 09:10:25 GMT

Hi Greg:

The standard "expectatation" of where to loook for things like this would/should be in '/usr/contrib' or '/usr/local'. Have a look at the manpages for 'hier(5)'.

Regards!

...JRF...

Re: Registering plain executables in SAM

GBR — Tue, 25 Jul 2006 09:29:42 GMT

Thank you very much. That answers my question.