In message <9507252249.AA18725@theos.com>,
	Theo de Raadt writes:
>> > Nsswitch is AFAIK done via /etc/resolv.conf, no need to start hacking that
>.
>> 
>> I disagree.  There are lots more databases that need to be configured
>> than just hosts...
>> 
>> I believe that a nsswitch.conf-like mechanism where the adminstrator
>> can select the type (file, dns, yp, hesiod, etc.) and resolution order
>> of database services for passwd, group, hosts, networks, protocols,
>> rpc, ethers, etc. would be a good thing.
>
>and many of those databases already have methods to say how/when they
>should lookup.
>
>basically, nsswitch.conf is wrong for (at least) passwd, group, and ethers
>because those files quite specifically in them say WHEN YP should be pulled
>in. YP should be pulled in with you hit the +. it is a lie to specify in
>nsswitch.conf that YP should be looked up first.

No, it's very useful for db's like passwd.  You could use it just like with
Solaris: specify whether you want `old' YP behavior, or NIS+/`new'-style
behavior.

>so what needs the nsswitch.conf? perhaps the other databases you mention.
>but it isn't hard to make the other databases also understand a + in them.
>or, as i've suggested many times before, @ for hesiod.

Filling the db's with tokens is ugly.  nsswitch.conf is an elegant,
centralized approach, and one of the actually nice things about Solaris
and company.

--
Jason Downs           | GCS/CM -d+ H(+++) s+:++ !g p? !au w+ v-(*)
downsj@xenotropic.com | C++(+++) UBAVHS++++$ P--- E--- N+++ W--- M-- V--
---------------------/ \-------------------------------------------------------
     Only the Feds could save children from abuse by burning them to death.