Hi,

I went through the code. I don't understand a lot of details, but at higher
level it seems to work this way. There are three authenticated methods - files,
dns, nis and compat modes. nis is meant for YP, dns is meant for hesiod and
compat mode seems to be a glue for YP & Hesiod or defines some common
functions. But as it is, it seems Hesiod is a default method and has dependency
on YP. (By this I mean Hesiod can't be compiled without YP. The snprintf which
is declared in stdio.h is included only with YP defined).

The nsswitch has only the compat method, the rest are not in the table. The
local password authentication scheme is also defined but not added to the
switch. I assume all the methods are well tested but left to the user's choice
to add it or leave it.  Is that right ?

Regards,
Srini.



--- Greywolf <greywolf@starwolf.com> wrote:
> Thus spake Luke Mewburn ("LM> ") sometime Today...
> 
> LM> Our "defacto" mechanism is that variables are tested against "no",
> LM> even "yes/no" variables, because there's no simple way to enforce
> LM> that such variables may only contain those two values, and it's easier
> LM> to have a single consistent check (== "no", or != "no") than cater for
> LM> all the various alternatives.
> 
> Minor observation:
> 
> MOST variables are thus tested, except for the few which are tested
> against (re_type) .if[n]*def, something which has caused me great
> consternation and confusion on occasion ("Hey, I just defined this
> to be 'no', why's it still defining/including this stuff?").
> 
> Perhaps it would be better to have one file in /usr/share/mk
> (bsd.defaults.mk? bsd.init.mk?) which sets up all the default values
> before /etc/mk.conf gets included, with no conditional checking (leave
> that to the "real" .mk files to fix up)?  Just a thought...
> 
> 				--*greywolf;
> --
> NetBSD: the free unix for the rest of us.


__________________________________
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/