we received only one answer but illuminating from Dr. Tom Blinn
<tpb_at_zk3.dec.com>, below we report the whole text.
Marco Lolli - Angela Peria
Bologna Astronomical Observatory
---------------------------------------------------------------------------
Did you in fact build kernels (on the clients) for use by the clients? The
kernel that is supplied to the clients initially is based on the generic
"/genvmunix" kernel (either by simply putting a network bootstrap wrapper
around the one from the distribution kit if you're running V3.2C or later,
or by building a "dataless" generic kernel if you're running V3.2B or one of
the earlier releases). That "generic" kernel doesn't have LAT built in; you
have to select LAT during the kernel definition (running doconfig on the
client) and build it into the client kernel. Also, you have to be sure that
you copy both /vmunix and /.vmunix from the client's kernel build area into
the client's root area -- the /vmunix is used by things that need to figure
out kernel symbol to name mapping, but the /.vmunix is the kernel that gets
booted, and if they're not the same (that is, /.vmunix was created from the
/vmunix by putting a network bootstrap wrapper around it), then you can get
situations like "I built LAT into the kernel but it doesn't work" because
you aren't really running the kernel you think you built. Double check this
by looking at the build dates on the /vmunix and /.vmunix in each client's
root (you can do this on the server, of course). If the /vmunix and
/.vmunix differ by more than a few seconds in terms of creation times, they
are probably not from the same build.
I use DMS all the time, and I have no problem getting things like LAT to
work as long as I get the clients set up correctly, but there are lots of
things about how the environment works that aren't well documented.
Tom
Received on Wed Jan 24 1996 - 10:59:27 NZDT