Hello Managers:
My original post for this summary is summarized below:
Using setld -i, I noticed that some of the software subsets
were marked as incomplete. So, I wanted to find out if
that was okay and/or what I should do.
NOTE: I now have a second post for this question. It is
titled: Software Installation Part II
--------------------
Thanks to Dr. Blinn and Stephen LaBelle for their responses.
In short, I used setld -d SUBSET_NAME to delete the incomplete
software subset and setld -l /mnt/ALPHA/BASE SUBSET_NAME to
re-install the software subset.
Since none of the subsets required a kernel rebuild, I did not
perform doconfig. I did decide to reboot the machine.
After rebooting, the result of all my work was >> Nothing Changed.
All the Software subsets that were incomplete before are still
incomplete.
-------------
Below are the two responses. I would summarize Dr. Blinn's, but
do not want to leave out any important information. I Included
Mr. LaBelles since it expressed what I thought I should be thinking:
------
>From Stephen LaBelle:
have never seen or heard of software sets being marked "Incomplete"
That is not normal.
Steve
----
>From Dr. Blinn:
There is one thing that will cause setld to flag a subset as "incomplete".
Every subset has a "control file" (/usr/.smdb./SUBSET.ctrl) that contains
information about the subset. If setld can't read the file or the file
doesn't have the data expected, the subset is marked "incomplete". There
are a number of lines in the file that setld needs to correctly process the
software subset.
If someone has tried to manually remove part of /usr/.smdb. and didn't know
how to do it right, that might result in this situation.
If you remove the subset and reinstall it, or remove the .lk file (which is
the flag to setld that the subset has been loaded) and reinstall it, then
you should be OK.
Tom
Received on Tue Jan 27 1998 - 22:05:48 NZDT