Creating depots

[Eli_pok]

Hi,
Have any one tried to create a depot that will install a "FULL" product?
For example, oracle's instalation contains only files so creating a depot that copies their files is not a problem, but creating a depot that will create the whole "shell" of oracle, filesystem group and user (maybe some other configurations).

Thanks ahead.

[SANTOSH S. MHASKAR]

Hi,

Not yet tried that, but it is a good idea to
create a depot for Oracle Software which
creates oracle user,group etc. and installs
required patches.


-Santosh

[Senthil Prabu.S_1]

Hi,
You can do it through post-install scripts, I guess. All your configurations should be defined in a script and should be called pd file.

HTH,
Prabu.S

[Eli_pok]

I know the option to run scripts threw pre/post install. What I ment is, if some one has a ready set of scripts and would like to share them.
In my group we have a "program" writen in shell , but it doesn't have the capabilities we want which sd-ux has.
So now I'm re-writing the scripts to add a remove option and make them work threw depots.
So the quation was if some-one has something similar that is ready.

[Matti_Kurkela]

The solution might be closer than you think...

Find an existing package that does what you need, and peek inside to see how it is done.
A .depot file is just a tar file with a different suffix and a strictly-defined directory structure packed inside. A directory depot (on a CD-ROM, or a .depot file copied to disk with swcopy) is already unpacked for easy examination.

For example, installing HP's SSH depot will shutdown the old sshd and ssh-agent processes if SSH is already installed, create some links differently depending on whether the system is a 32- or 64-bit one, and create a new user for sshd's privilege separation mechanism. If there are no pre-existing SSH host keys, it will create them too. That should contain a lot of useful ideas.

If you can do everything needed to create the environment for your product on the command line, just write the commands into a file and you'll have your script right there.

MK

[Eli_pok]

thanks for your answear that helps a lot, but still there are some open issues (the most important two - for me).
1. Creating an removing a FS
2. And the hardest script (as I see it) modifing kernel parameters (a script that would be able to scheduale a modification to the next boot and take in mind if the scirpt was activated several times before the boot remembering the largest value set).