...
- You must first determine the name of the subset that contains the files you wish to copy
- method 1: use
setld -i | grep -i <keyword>to find the name of the subset - method 2: look for a file in the "inventory" files of all subsets:
# cd /usr/.smdb.# grep <filename> *.inv
- method 1: use
- 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 - 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> - 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/subset-files.cpio - Then copy /var/tmp/subset-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/subset-files.cpio 2>/dev/null | while read file; do if [ -f /$file ]; then echo "collision: /$file"; fi; done - If there are no collisions, unpack with:
# cd /# cpio -idv -I/path/to/subset-files.cpio - If there are any collisions, you will have to deal with those carefully before unpacking.
...