topic software depot setup in Operating System - HP-UX

software depot setup

valcor — Tue, 10 Jul 2007 09:16:52 GMT

Hello

Can someone explain to me exactly what will the software depot setup will do? Will it just copy the depot or will it actually do an install from the depot? If it is just copying, where will it be copied to and how much space will it require? If it is copying the depot, can I change the default to where I want it copied to?

Thanks in advance.

Re: software depot setup

Torsten. — Tue, 10 Jul 2007 09:18:49 GMT

Are you asking about a special depot?
(because you are asking about the size ...)

The swinstall process will do some checking and install the software included in the depot.

Re: software depot setup

valcor — Tue, 10 Jul 2007 09:23:42 GMT

Sorry, I was unclear with my question. This is during the initial setup of the Ignite server. There is a step "Software depot setup". I was given 3 options, copy from a CD/DVD, use CD/DVD or use Installed Depot.

Re: software depot setup

Steven E. Protter — Tue, 10 Jul 2007 09:24:52 GMT

Shalom,

Lets say I have a depot in a directory called /depot

cd /depot
du -sk

If I use the create_depot command HP provides with patch downloads or swcopy myself the resulting depot will be approximately the size of the software I swcopy (both methods actually use swcopy). Give or take a few percentage points.

swcopy has a -p command which previews the software copy and might give you more accurate data.

SEP

Re: software depot setup

James R. Ferguson — Tue, 10 Jul 2007 09:27:26 GMT

Hi:

One uses 'swcopy' to copy software into a 'depot' for installation. Using 'swcopy' does *not* cause any installation. Installation is performed by 'swinstall'.

The space required will be somewhat more than the sum of the sizes of the individual components. You can specify the depot location using any valid absolute path.

There is no need to explicitly register a depot with 'swreg' unless you intend to use the depot remotely from another server.

It is very common to specify '-x enforce_dependencies=false' when building or adding a depot of patches. This allows patches to be added to a depot when all of their co-requisites or dependent patches are *not* ultimately contained within the depot. That is, you defer the dependency analysis until you actually install the contents of the depot with 'swinstall'. If you attempt to perform the 'swcopy' with '-x enforce_dependencies=true' you must satisfy the requirement wholly with the depot contents.

For example:

# swcopy -v -s BUNDLENAME -x enforce_dependencies=false \* @ /var/tmp/swdepot

...would copy all of the contents of BUNDLENAME into a depot named /var/tmp/swdepot (a common default one).

Regards!

...JRF...

Re: software depot setup

Scot Bean — Tue, 10 Jul 2007 18:24:36 GMT

It copies the install media to a default location or one you choose so you can Ignite or Install from the Ignite server to multiple, remote targets.

Re: software depot setup

skt_skt — Tue, 10 Jul 2007 20:59:17 GMT

also Just try "swcopy" and it will take u to a CLI interactive menu..It ask source,dest etc and more easy