Thanks for the input! This will cut down on the number of reboots for all
the installs that we do. This installation is done at customer sites where
time is of the essence...
Wendy
The question was:
>
>
>I have a question about rebuilding and rebooting the system after
>installing subsets. We load DecEvents, SS7, TruCluster, WDA, etc.
>After each setld each subset instructs you to rebuild the kernel and
>reboot. Can I just do one doconfig at the end of all of the setld's?
>
>I would think that the kernel is rebuilt and the system rebooted to enable
>the subset you just loaded. The files necessary for the make are still
>there for all the subsets previously loaded, and would be included in
>any subsequent doconfig. Or, am I missing something?
>
==========================================================
You pretty much got it. When a subset that modifies kernel components or adds
additional options is loaded, it should (if it's working correctly) add to the
appropriate kernel configuration databases all the information needed to build
a kernel later on. If you don't build a new kernel right away, then the next
time you do build a kernel, all the mandatory pieces should be incorporated.
One thing the kit documentation might not tell you is that if you've built a
new kernel after installing the first product that creates the .product.list
file in /sys/conf, and then you build another kernel using the existing config
file, you will NOT get the new components. You only pick up the new stuff if
you run doconfig with NO arguments, and ideally while you're running with the
/genvmunix kernel (which should see all your default supported hardware).
Of course, you probably should do the build after each product installation,
and it's possible for the product installation to have files that need to be
configured AFTER you reboot, in which case, it might be adding entries into
the /sbin/it.d directory hierarchy -- but you could check for that.
The reason why it's useful to do the build after each product addition is that
if there are any incompatibilities between the products, you'd be more likely
to find it out at that point and perhaps be able to resolve it. If you wait
to do the kernel rebuild until AFTER all the products are loaded, figuring out
what's causing an incompatibility can be a nightmare.
Tom
=====================================================
Rebuilding the kernel after all the subsets were loaded is the right way to
go. There's nothing to be gained by rebuilding it at each intermediate
step, as those kernels will just get overwritten by your subsequent builds.
-- - keith
Received on Fri Apr 23 1999 - 01:09:18 NZST