NIS configuration

[mod+linux-fai at std.com]

>>Yah, it's too bad the NIS gets defined if YPDOMAIN is defined.
>
>I'm curious, why would this be bad?  If you have YPDOMAIN defined, 
>then wouldn't you *want* NIS?  If you don't want NIS, then don't 
>define YPDOMAIN.  Wouldn't you simply create a class which doesn't 
>have NIS, and therefore doesn't define YPDOMAIN?


I can see why you'd be curious.  The problem for me
is that my DHCP server has a single global nis-domain
definition that gets handed to all clients, and which
is appropriate for all clients that will be living on
that server's network.  But I sometimes temporarily
connect client machines to that server in order that
they can use FAI to load them up with a configuration
that will later be used when those machines are moved
onto a private LAN that doesn't have NIS.

I could lose the global definition, but then I'd
be obliged to define nis-domain on a per-client
basis, right?  I'd rather that FAI didn't helpfully
make incorrect assumptions, and that when I say
NONIS, I really do actually mean it...