Page Comparison

...

1. You must first determine the name of the subset that contains the files you wish to copy
   
   1. method 1: use setld -i | grep -i <keyword> to find the name of the subset
   2. method 2: look for a file in the "inventory" files of all subsets:
      cd /usr/.smdb.
grep <filename> *.inv
2. Now that you know what the name of the kit is, you can look at its inventory file. In this example, I will use OSFSER3D440 as the kit name.
   more OSFSER3D440.inv
3. The inventory is formatted into columns. The man-page "stl_inv" describes the format. Briefly, the columns are:
   <flags> <size> <checksum> <uid> <gid> <mode> <date> <revision> <type> <pathname> <link-to> <subset-name>
4. It is probably enough to create a cpio-archive using the <pathname> column from the inventory. That can be done like this:
   cd /
awk '{print $10}' /usr/.smdb./OSFSER3D440.inv | cpio -ov -O/var/tmp/driversubset-files.cpio
5. Then copy /var/tmp/driversubset-files.cpio to the target system. Before you unpack it, make sure there are no collisions with this command:
   sh # (if you aren't already running /bin/sh or /bin/ksh)
cpio -it -I/path/to/driversubset-files.cpio 2>/dev/null | while read file; do if [ -f /$file ]; then echo "collision: /$file"; fi; done
6. If there are no collisions, unpack with:
   cd /
cpio -idv -I/path/to/driversubset-files.cpio
7. If there are any collisions, you will have to deal with those carefully before unpacking.

Now the files should be on the target system. You may need to perform additional steps to make the driver subset active. I don't remember the details. It may help to look at the "Subset Control Program", which is in /usr/.smdb./<kit-name>.scp. You may find the "stl_scp" man-page useful.

...