Nekochan Net

I've been looking at the SD-UX install disks for HP-UX, and I'm a bit flummoxed. I understand the packaging systems used by SGI, Sun, IBM, xBSD, Linux, etc, but I am completely confused by the HP system. Loading up a disk in the install program and it happily goes through init and install scripts, but mount the disk and look at the filesystem and it has a tree for the software that corresponds with where it goes on the filesystem, but no scripts.

I figure there must be some species of multiple-filesystem-overlay setup with the install scripts in a separate partition/slice/whatever, which seems like an odd way to do it, and the HP SD-UX documentation doesn't elaborate much (just says "to build package use this tool and feed this into it" sort of thing).

Next step I suppose is to look at the raw disk with a hex editor, provided that I'm sufficiently interested, but I thought I'd toss it out here first.

_________________
Damn the torpedoes, full speed ahead!

Systems available for remote access on request.

(single-CM)

Should be rolled into .depot files? You can swlist -s /path/to/depotfile/package.depot
That should tell you the packages inside. Actually they're just tar files with a post-install script
that updates the package dbase after it's swinstall -s ..rah rah. Tried running sam/smh and pointing
it at the depot? It's a bit gui-ish.

_________________
Al Boyanich
adb -w -P "world> " -k /dev/meta/galaxy/ksyms /dev/god/brain

I can install files just fine, it's just a matter of curiosity. When you insert a HP CD-ROM or DVD-ROM (I've tried it with 11iv1 MCOE, and 10.20 for 700s) and explore the directory structure you get (under the package name) a list of the files and where they go in the system, but there are no preinstall/postinstall scripts either in the product directory or in an obvious scripts directory.

There must be some hidden partition of the disk that holds the scripts, I guess. It's just so different from other system packaging formats, where you do have a file or set of files that have an archive of the installed files and instructions (scripts/permissions/etc).

I haven't looked at .depot files yet, just at the distro CD's. .Depots (how do you capitalize this? Computer discussions always create interesting punctuation quandaries) might be a bit more conventional.

_________________
Damn the torpedoes, full speed ahead!

Systems available for remote access on request.

(single-CM)

This gets nitty gritty quite quickly...

http://www.massconfusion.com/tim/notes/hpux_depot_create_howto.txt

_________________
4xRS6K 2xHP9K 6xSUN 1xDEC 14xMAC 7xPC 2xPS2

I did find some more out about it - it looks like much of that information is stored in the {CD_ROOT}/catalog/{product_name} hierarchy, but it's difficult to figure out. I guess that's because HP mixes their installation programs and their licensing scheme, rather than something like IRIX or OpenVMS where they are separate.

I'm poking into how things are done, though, and slowly figuring them out.

_________________
Damn the torpedoes, full speed ahead!

Systems available for remote access on request.

(single-CM)