A/UX 2.0: How To Stop "newconfig" From Dumping Modules


Article Change History
----------------------
08/31/92 - REVIEWED
* For technical accuracy.


I have a problem with newconfig.

It seems that newconfig does not do an "eupdate" after building a new kernel.
Therefore, when the system starts up and finds something strange, it takes the
old kernel back from Eschatology. This leads to strange problems, like missing
modules in the kernel.

Is it possible to include an eupdate in the script so the Eschatology
information is automatically updated after a new kernel build?

You are correct in stating that newconfig does not do an eupdate.  However, we
do not think that is the cause of your problem.

When the system is started up, and something "strange" is found (such as a new
card installed), newconfig is run to rebuild the kernel.  The file, /newunix,
is used as the base for the new kernel.  Since this is a minimal kernel,
modules that you had previously installed will be missing.
     
It should be possible to write your own script that first called newconfig
and then eupdate to save the new kernel in the Eschatology partition.  When the
system finds an invalid kernel and builds a new one, you could then restore
your kernel from Eschatology.

Another method that many people use is to copy /newunix to /newunix.save and
install the modules you want in /newunix. Then, anytime your kernel is rebuilt
from this /newunix, you will automatically have all of the modules you want.


Published Date: Feb 18, 2012