Hi Folks,
We just had some interesting problems with trying to remove some SW
subsets using setld. The problem started when we thought that maybe
we didn't get all the optional components that we thought we needed
when we installed the O/S (DUNIX v4.0B, v564 on aa AS 500/500).
So we installed almost all the stuff that showed up: LSM, AdvFS, ATM,
C2, RIS, and a couple other items. However, when we try to boot up with
the new kernel (which ended up being 50% bigger than the previous version),
we got some error messages on the console complaining about not fining
primary swap and dump space. I didn't catch the error message before it
as the screen flashed by too quickly, but my guess is that it was trying
to dump core. The boot up attempt would repeatedly fail, so we had to
push the reset button to stop it.
So we booted the machine up from the CD, and went into the UNIX shell to
manually copy the genvmunix to vmunix so it would boot up properly.
(I guess this could have been done from the console by specifying the
boot file?) Once up, we tried to remove all the new SW sets installed,
and tried to rebuild the kernel. The problem then, was that doconfig
procedure still tried to look for files needed by all those SW sets.
It took a while to figure out that we had to manually edit the config
file to take out all those options. However, the doconfig was still
looking for files for AdvFS, even though we could find no reference for
it in the config file. So, we added that back into the system, and the
build procedure completed. We're not sure how well that runs right now,
as the system is inaccessible for the next 10 hours.
So my questions (finally) are:
Are the install/de-install procedures supposed to automatically change
all the related files so that the kernel may be built properly? Since
this is obvisouly not working, how do I manually force AdvFS out of our
system?
Thanks for any clues.
eyc
Received on Tue Mar 24 1998 - 07:50:45 NZST