SEO

#1 (**permalink**) 01-17-2008, 06:00 AM

Normally we do hp-ux patches using depot files, however this time, we
have a single PHSS patch to install.

I can't find any documentation on how to install an individual patch,.

Scott

#2 (**permalink**) 01-17-2008, 06:00 AM

mohnkern wrote:
> Normally we do hp-ux patches using depot files, however this time, we
> have a single PHSS patch to install.
>
> I can't find any documentation on how to install an individual patch,.
>
> Scott
>

Not sure what you mean here.. since usually patches are delivered in
shar's that contain the depot file, even for a single patch. (You can
bundle patches into larger depots... but typically there's a
PHKL_*****.depot file involved...)

If you have a shar file, just sh <foo>.shar and you should get the
..text and .depot files -- installation instructions would be in the
..text file. Typically this is:

swinstall -x autoreboot=true -x patch_match_target=true -s
/tmp/PHSS_foo.depot

Hope this helps -- but if not, let us know what this PHSS looks
like and we try to go from there.

Don

#3 (**permalink**) 01-17-2008, 06:00 AM

On Jun 8, 10:45 am, Don Morris <dmor...@cup.hp.com> wrote:
> mohnkern wrote:
> > Normally we do hp-ux patches using depot files, however this time, we
> > have a single PHSS patch to install.
>
> > I can't find any documentation on how to install an individual patch,.
>
> > Scott
>
> Not sure what you mean here.. since usually patches are delivered in
> shar's that contain the depot file, even for a single patch. (You can
> bundle patches into larger depots... but typically there's a
> PHKL_*****.depot file involved...)
>
> If you have a shar file, just sh <foo>.shar and you should get the
> .text and .depot files -- installation instructions would be in the
> .text file. Typically this is:
>
> swinstall -x autoreboot=true -x patch_match_target=true -s
> /tmp/PHSS_foo.depot
>
> Hope this helps -- but if not, let us know what this PHSS looks
> like and we try to go from there.

>
> Don

Actually, I've found if you select a single patch (instead of
several), it's not delivering them as a depot file, which is pretty
annoying. I may have another solution, which is to mark an additional
file for patching, then unmark it, and see if it gives me a depot
then. I I just select a single patch it gives me a file in the form
of PHCO_XXXXX or PHSS_____ which looks like a shell script, but when
you run it, it doesn't do anything.

#4 (**permalink**) 01-17-2008, 06:00 AM

On Jun 8, 2:50 pm, mohnkern <mohnk...@gmail.com> wrote:

>
> Actually, I've found if you select a single patch (instead of
> several), it's not delivering them as a depot file, which is pretty
> annoying. I may have another solution, which is to mark an additional
> file for patching, then unmark it, and see if it gives me a depot
> then. I I just select a single patch it gives me a file in the form
> of PHCO_XXXXX or PHSS_____ which looks like a shell script, but when
> you run it, it doesn't do anything.- Hide quoted text -
>
> - Show quoted text -

I just downloaded a single patch, and it came as a shell archive, just
as Don explained. You need to do "sh <downloaded_name>" to extract it.

#5 (**permalink**) 01-17-2008, 06:00 AM

On Jun 8, 10:05 am, mohnkern <mohnk...@gmail.com> wrote:
> Normally we do hp-ux patches using depot files, however this time, we
> have a single PHSS patch to install.
>
> I can't find any documentation on how to install an individual patch,.
>
> Scott

Scott, last I did a single patch, once you unshared it, I thought it
came with both a .depot file and a .text file with the text file
containing installation and other information about the patch.

Charles R. Whealton
Charles Whealton @ pleasedontspam.com

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

A really dumb question